Skip to main content
Glama

n8n_tools_help

Access documentation and usage guides for n8n workflow automation tools to understand available capabilities and implementation methods.

Instructions

Get documentation and usage guide for n8n MCP tools. Call this first to understand available capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoTopic to get help about. "overview" for general guide, "workflows" for workflow management, "executions" for execution management, "nodes" for common node types, "examples" for usage examples.

Implementation Reference

  • The main handler function for 'n8n_tools_help' that retrieves and returns documentation content based on the provided topic parameter (defaults to 'overview').
    n8n_tools_help: async (
      args: Record<string, unknown>
    ): Promise<ToolResult> => {
      const topic = (args.topic as string) || 'overview';
      const content = DOCUMENTATION[topic as keyof typeof DOCUMENTATION] || DOCUMENTATION.overview;
    
      return {
        content: [
          {
            type: 'text' as const,
            text: content,
          },
        ],
      };
    },
  • Tool schema definition including name, description, and inputSchema for the 'n8n_tools_help' tool.
    {
      name: 'n8n_tools_help',
      description: 'Get documentation and usage guide for n8n MCP tools. Call this first to understand available capabilities.',
      inputSchema: {
        type: 'object',
        properties: {
          topic: {
            type: 'string',
            enum: ['overview', 'workflows', 'executions', 'nodes', 'examples'],
            description: 'Topic to get help about. "overview" for general guide, "workflows" for workflow management, "executions" for execution management, "nodes" for common node types, "examples" for usage examples.',
          },
        },
      },
    },
  • Registration of tool definitions: 'n8n_tools_help' is included via spread of documentationTools into the allTools array used by the MCP server for listing tools.
    export const allTools: ToolDefinition[] = [
      ...documentationTools,  // Documentation first for discoverability
      ...workflowTools,
      ...executionTools,
    ];
  • src/server.ts:108-110 (registration)
    Handler dispatch registration: Routes calls to 'n8n_tools_help' by checking against documentationToolHandlers object and invoking the matching handler.
    if (name in documentationToolHandlers) {
      const handler = documentationToolHandlers[name as keyof typeof documentationToolHandlers];
      return handler(args);
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the tool's behavior as retrieving documentation, which implies a read-only, non-destructive operation. However, it lacks details on output format, potential errors, or any rate limits. The description adds basic context but misses richer behavioral disclosure expected for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences that are front-loaded with the core purpose and followed by usage guidance. Every sentence earns its place by providing essential information without redundancy or fluff, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter with full schema coverage) and lack of output schema, the description is mostly complete. It clearly states the purpose and when to use it. However, without annotations or output schema, it could benefit from more details on what the documentation output looks like (e.g., format, structure) to fully guide the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, documenting the single parameter 'topic' with its enum values and descriptions. The description does not add any parameter-specific information beyond what the schema provides. With high schema coverage and only one parameter, the baseline is strong, but no extra semantic value is added in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool's purpose: 'Get documentation and usage guide for n8n MCP tools.' It specifies the verb ('Get') and resource ('documentation and usage guide'), and distinguishes itself from sibling tools by focusing on help/documentation rather than operational actions like creating or managing workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: 'Call this first to understand available capabilities.' This clearly indicates when to use this tool (as an initial step for learning) versus alternatives (the sibling tools for actual operations), offering strong contextual direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alicankiraz1/cursor-n8n-builder'

If you have feedback or need assistance with the MCP directory API, please join our Discord server