Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

workflow_get_node_parameter

Read-only

Get metadata plus either a full value or a targeted chunk for one node parameter. Use this instead of workflow_get_node for very large text/code parameters.

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": {
      "workflowId": "<workflowId>",
      "nodeId": "<nodeId>",
      "parameterId": "<parameterId>"
    },
    "name": "workflow_get_node_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node
endLineNoOptional 1-based end line for chunked retrieval
startLineNoOptional 1-based start line for chunked retrieval
workflowIdYesThe workflow ID
parameterIdYesThe ID of the parameter to retrieve
maxCharactersNoOptional maximum number of characters to return (default: 12000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile and closed-world scope are covered. The description adds that retrieval can be a 'targeted chunk' rather than the whole value, but does not disclose truncation behavior, whether a truncated response is flagged, or what happens when startLine exceeds the value's length. With annotations carrying the safety burden, this is an adequate but thin contribution.

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 sentences, zero waste, with the scope and return shape stated first and the sibling-routing rule immediately after. Every sentence earns its place.

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?

With no output schema, the description does carry some of the return-value burden and states it returns metadata plus a full value or a chunk. That is enough for an agent to call the tool correctly given full schema coverage and read-only annotations, though details like metadata contents and truncation signaling are left implicit.

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 all six parameters, including the startLine/endLine chunking pair and the maxCharacters default of 12000, are already documented in structured fields. The description only echoes the chunking concept via 'targeted chunk' and adds no rules about how startLine/endLine interact with maxCharacters. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource ('Get metadata plus either a full value or a targeted chunk for one node parameter') and explicitly distinguishes it from the sibling workflow_get_node. An agent can separate the two tools without inspecting either schema.

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?

It names the alternative (workflow_get_node) and the condition that selects this tool ('very large text/code parameters'), which is clear routing guidance. It stops short of explaining when to prefer line-range chunking over maxCharacters, so the agent still has to infer how to drive the chunk parameters.

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

All Spaces by Peakflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources