n8n-asistans
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_n8n_infoB | Search the latest n8n resources for a given query. Args: query: The query to search for (e.g. "HTTP Request node") resource_type: The resource type to search in (docs, workflows, community) - docs: General n8n documentation - workflows: Example workflows (will search for "n8n example {query}") - community: Community forums for issues and questions Returns: Text from the n8n resources |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect. The tool's purpose is clearly defined as searching n8n resources, and no other tools exist to cause confusion.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'get_n8n_info' follows a clear verb_noun pattern, but consistency across multiple tools cannot be assessed.
A single tool for a server named 'n8n-asistans' feels too thin for the apparent scope, as it only offers search functionality without any CRUD operations or broader management capabilities for n8n resources. This is a borderline case leaning toward inadequacy for a typical assistant server.
The tool surface is severely incomplete for an assistant server, as it only provides search functionality without any ability to create, update, delete, or manage n8n workflows or resources. This will likely cause agent failures when trying to perform comprehensive tasks beyond simple queries.