Skip to main content
Glama

Get node parameters

get_td_node_parameters
Read-only

Read parameters, inputs, and outputs of a node, with options to filter by parameter names or omit I/O lists to reduce context usage.

Instructions

Read-only: read the current parameters (and inputs/outputs) of one node. Returns {path, type, name, parameters, inputs, outputs}. Pass keys to project specific parameters or omit_io:true to drop the inputs/outputs lists. Use compare_td_nodes to diff two nodes' parameters at once. Token economy: pass keys to fetch only the parameters you care about and omit_io:true to drop inputs/outputs — a full parameter dump is large.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysNoOnly return these parameter names (case-sensitive). Omit to return all parameters.
pathYesFull path of the node to inspect.
omit_ioNoDrop the inputs/outputs lists from the result to save context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
pathYes
tagsNo
typeYes
colorNo
flagsNo
nodeXNo
nodeYNo
errorsNo
familyNo
inputsNo
commentNo
outputsNo
wires_inNo
parametersYes
already_existedNo
parameter_warningsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds specifics about the return fields and warns that a full parameter dump is large, providing context beyond the annotations.

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 concise paragraph with no redundant information. It front-loads the core purpose and efficiently adds usage guidance and token economy tips.

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

Completeness5/5

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

Given the output schema exists, the description sufficiently covers purpose, usage, parameter behavior, and alternative tools. No gaps for this read-only tool with 3 parameters.

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?

Schema coverage is 100%, but the description adds practical guidance: 'project specific parameters' for keys and 'drop the inputs/outputs lists' for omit_io, clarifying the effect of parameters beyond the schema descriptions.

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 clearly states it is a read-only operation to read node parameters and inputs/outputs, listing the return structure. It distinguishes from sibling compare_td_nodes by mentioning it for diffing two nodes.

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?

Provides explicit when-to-use (read-only node inspection) and when-not (use compare_td_nodes for diffing). Also gives token economy advice on using keys and omit_io to reduce data.

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/Pantani/tdmcp'

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