Skip to main content
Glama

Read parameter modes

read_parameter_modes
Read-only

Inspect each parameter of a node: reports its mode, evaluated value, and raw expression/export/bind strings. Use non_default_only to surface parameters lost in a plain value copy for faithful serialization.

Instructions

Read-only: for each parameter of a node, report its mode (CONSTANT / EXPRESSION / EXPORT / BIND), its evaluated value, and its raw expression / bind-expression / export-source strings. Use this to faithfully serialize a network for round-trip editing, diffing, or debugging — the evaluated value alone hides which parameters are driven by expressions or exports. Set non_default_only to surface only the parameters that would be lost in a plain value copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull path of the node whose parameters to inspect.
keysNoOnly report these parameter names (case-sensitive). Omit for all parameters.
non_default_onlyNoOnly return parameters whose mode is not plain constant (i.e. expression/export/bind) — the ones that matter for a faithful round-trip.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
typeYes
nameYes
parametersYes
probeNo
warningsYes
Behavior4/5

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

The description begins with 'Read-only,' consistent with the annotation 'readOnlyHint: true.' It details the exact data reported (mode, value, raw strings) and the use case. It adds context beyond the annotations by clarifying the scope and purpose, though it doesn't mention any additional behavioral traits like response format or pagination.

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?

Two well-structured sentences: the first defines the tool's action and output, the second provides usage guidance and a parameter hint. No redundant words; each sentence earns its place.

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 tool's complexity (3 parameters, 1 required, output schema provided), the description covers purpose, output details, and usage context. The output schema handles return value specification, so no further detail is needed.

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 100% schema coverage, the baseline is 3. The description adds significant value for the 'non_default_only' parameter by explaining its purpose in the context of round-trip editing. It also reinforces the overall intent, making parameter semantics clearer than the schema alone.

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 the verb 'report' and the resource 'parameter modes' of a node, listing the exact information returned (mode, evaluated value, raw strings). It distinguishes this tool from siblings like 'get_td_node_parameters' by focusing on modes for round-trip editing, diffing, or debugging.

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?

The description explicitly tells when to use the tool: for faithfully serializing a network for round-trip editing, diffing, or debugging. It explains why evaluated values alone are insufficient. While it doesn't name specific alternatives, it implies that other tools might be used for plain value copies.

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