relative-interpreter-mcp

Run node

run_node

Execute a function node's pipeline and settle the reactive cascade. Optionally provide manual input overrides for the node's in-ports.

Instructions

Execute a function node's pipeline and settle the reactive cascade.

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": {
      "node": "<node>"
    },
    "name": "run_node"
  }
}

Input Schema

Name	Required	Description	Default
`node`	Yes	Name or name#uuid of a function node in the current scope.
`inputs`	No	Manual overrides for in-ports.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Aug 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Settle the reactive cascade' hints at cascading side effects but does not explain what those effects are, whether they are reversible, or what permissions are needed. It also does not mention the return value or any potential destructive/irreversible consequences, making it insufficiently transparent.

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?

The description is a single concise sentence, front-loaded with the primary action ('Execute a function node's pipeline'). However, the second clause 'and settle the reactive cascade' is vague and potentially confusing, lowering the efficiency of communication. It is still structurally compact and uncomplicated.

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

Completeness2/5

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

For a tool with two parameters, one required, and no output schema, the description should clarify what the tool returns, what side effects occur, and the meaning of the 'reactive cascade'. It does none of these, leaving the agent with insufficient context to predict the tool's full impact. The presence of nested objects in inputs makes this guidance even more critical.

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 coverage is 100%, and each parameter has a description in the schema: 'node' as a string and 'inputs' as an object for overrides. The tool description adds no extra parameter-specific detail beyond the schema. Given full schema coverage, a baseline of 3 is appropriate, but no added value earns a higher score.

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 clearly states the tool executes a function node's pipeline, using the verb 'Execute' and specifying the resource. The phrase 'settle the reactive cascade' adds a sense of broader side effects but is somewhat jargon-heavy, slightly obscuring the primary purpose. It distinguishes from sibling model-management tools, but does not explicitly name alternatives.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only describes what it does, leaving the agent to infer the appropriate context from the name and sibling list. This is a clear gap.

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