Skip to main content
Glama
Sign In

Gydmation

by io.github.hacrootechnologies
OverviewDiscussionsAdmin

Search n8n nodes

search_nodes
Read-only
Search Gydmation's n8n node catalog by keyword (name, n8n type string,
usage notes): every official n8n node plus maintained community nodes
(those carry community_package -- the user installs it in n8n first).
Use before writing any node; then get_node for the full definition.

Args:
    query: e.g. "slack", "webhook", "schedule", "postgres".
    limit: Maximum matches.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds real context beyond that: the catalog covers every official node plus maintained community nodes, and results carrying community_package mean the user must install the package first. It doesn't mention result count behavior or ranking, but the added domain context is substantial.

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

Conciseness4/5

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

Core purpose and the get_node handoff come first, followed by a compact Args block. Slightly list-like formatting and a repeated 'n8n' phrasing cost a little, but every sentence carries information.

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?

There is no output schema, and the description partially compensates by naming a returned field (community_package) and implying match lists. What's missing is anything about match/limit interactions or the shape of a result entry, but an agent can call this confidently.

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?

With 0% schema description coverage the description must carry the load, and it mostly does: query is explained as keyword matching against name, type string, and usage notes, with four concrete examples. Limit is defined only as 'Maximum matches' and omits the schema default of 10, leaving one gap.

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?

States a specific verb and resource ('search Gydmation's n8n node catalog by keyword') and names the fields searched (name, n8n type string, usage notes). It also distinguishes itself from the lookup sibling by directing the reader to get_node for full definitions.

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

Usage Guidelines4/5

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

Gives explicit sequencing: use before writing any node, then get_node. That is clear usage context, though it doesn't state exclusions (e.g., when to browse rather than search, or behavior on zero results).

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

All Gydmation toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources