relative-interpreter-mcp

Get script source

get_script_source

Retrieve the read-only script source of a function node by scriptPath. View the exact code for inspection or debugging.

Instructions

A function node's script source, read-only.

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": {
      "scriptPath": "<scriptPath>"
    },
    "name": "get_script_source"
  }
}

Input Schema

Name	Required	Description	Default
`scriptPath`	Yes	The node's scriptPath, as shown in the outline.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Aug 11, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state 'read-only,' which is a useful trait, but it does not mention return format, error behavior, or any prerequisites. This is minimal added value beyond the obvious 'get' semantics.

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 phrase with every word earning its place. It is appropriately sized for a simple getter tool and contains no redundancy or filler.

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?

For a tool with one parameter, no output schema, and no annotations, the description sufficiently conveys the core behavior: retrieving a function node's script source as a read-only operation. The return value is implied by 'script source,' and the parameter is fully covered by the schema. Minor gaps exist around domain context (what a function node is) but are not critical for a straightforward getter.

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?

The single parameter scriptPath is already fully described in the schema with 100% coverage. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 identifies the tool as returning a function node's script source and explicitly marks it as read-only. While it lacks an action verb, the title 'Get script source' supplies the verb, and the description unambiguously distinguishes this from sibling tools like get_model or get_scope by focusing on script source.

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 gives no guidance on when to use this tool versus alternatives. It neither states typical use cases nor mentions exclusions or related tools. The context signals show many sibling tools, but no differentiation is provided.

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