MCP enabled n8n workflows should have description #19
Replies: 3 comments 5 replies
-
|
@HubertReX, maybe there is conflicting documentation, and if there is please let me know. But CAAL actually receives its tool instruction from the Notes within the Webhook node. For some reason the description is not passed through MCP. Originally was going to use description but ran into the wall, so some of the workflows may have a description that looks like instructions. I could clean that up. So all the included workflows in the n8n-workflows folder should have descriptions in the webhook notes. |
Beta Was this translation helpful? Give feedback.
-
|
Caal is not correctly using the tool, I mean It's showing in the UI that the tool it used is correct(of n8n) but still it shows some error occured or errors like request.tools something |
Beta Was this translation helpful? Give feedback.
-
|
A few things going on here:
The model sees the prompt say "use hass_control", tries your custom tool first, it fails, then tries to fall back to what the prompt says - but that tool doesn't exist. What model are you using?
|
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
As I understand, n8n workflows that have MCP access enabled should have a description. See below:
This is a hint for an AI tool that wants to use it on how it works and what parameters should be provided. I'm not sure if it's a bug, since CAAL, to some extent, is still able to use them. Still, I believe it would work better with a description. I haven't found workflow descriptions in the repo. Tried to write them on my own, but still, it would be better to get the original intent from the author 😉
Beta Was this translation helpful? Give feedback.
All reactions