Skip to main content
Glama

get_node_definitions

Get detailed schema for all available node types including inputs, outputs, and default values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_node_definitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category: input, generation, processing, output, utility
nodeTypeNoGet definition for a specific node type
nodeTypesNoGet several needed node definitions in one call. Use instead of repeated lookups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / nodeTypes
      Added value: +{
      +  "description": "Get several needed node definitions in one call. Use instead of repeated lookups.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 12,
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the behavioral disclosure burden. It usefully explains that the tool returns schemas including inputs, outputs, and default values, but it does not explicitly state that the operation is read-only, nor does it describe performance characteristics, filtering behavior, or response structure.

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 a single efficient sentence that front-loads the core purpose and returned content. There is no redundant or wasted wording.

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

Completeness3/5

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

The tool has three optional parameters and no output schema, so the description should sufficiently explain what is returned and how filtering works. It covers the return content well, but it does not mention that callers can filter by category, request a specific node type, or batch multiple node types, leaving some contextual gaps relative to the schema's capabilities.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameter schema already documents category, nodeType, and nodeTypes thoroughly. The description adds no additional parameter-specific meaning beyond what is already in the schema, making the baseline score of 3 appropriate.

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

Purpose4/5

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

The description states a specific verb ("Get") and resource ("detailed schema for all available node types") along with the returned content (inputs, outputs, default values). It distinguishes itself from a simple list tool by emphasizing detailed schemas, though it does not explicitly name or contrast with sibling tools such as list_available_nodes.

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

Usage Guidelines3/5

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

The description implies usage by stating that it retrieves detailed schemas, but it does not explicitly state when to use this tool versus list_available_nodes or other related tools. No exclusions, prerequisites, or alternative recommendations are provided in the description itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.