relative-interpreter-mcp

Link external submodel

link_external_submodel

Add a submodel node that references an external Relative model directory. Path is validated against the server's allowlist to ensure only permitted directories are linked.

Instructions

Add a submodel node backed by a model directory outside this one. The service validates the path against its RELATIVE_EXTERNAL_ROOTS allowlist and refuses anything outside it.

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": {
      "name": "<name>",
      "ref": "<ref>"
    },
    "name": "link_external_submodel"
  }
}

Input Schema

Name	Required	Description
`ref`	Yes	Absolute path to an external Relative model directory.
`name`	Yes
`writable`	No	Default false. Writes also need the server to allow them.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Aug 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses a critical behavioral trait: the service validates paths against RELATIVE_EXTERNAL_ROOTS and refuses anything outside it. This adds meaningful context beyond the basic action, though it does not mention side effects, permissions, or return details.

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 two tightly written sentences, front-loaded with the core action and followed by a key constraint. Every word earns its place, with no fluff or repetition.

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

Completeness3/5

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

Given the tool has 4 parameters, no output schema, and no annotations, the description covers the core purpose and a critical restriction but is incomplete in some areas. It does not mention return values, failure behavior beyond path refusal, or any required permissions, leaving an agent to infer these from context.

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 50%, so the description must partially compensate. The description clarifies 'ref' by explaining it points to an external model directory and is subject to an allowlist, adding meaning beyond the schema. However, 'name' and 'description' remain undocumented, and the description does not systematically address all parameters.

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 uses a specific verb ('Add') and identifies the resource ('submodel node') with a clear qualifier ('backed by a model directory outside this one'). This distinguishes it from siblings like enter_submodel or create_model, which involve different operations.

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 provides clear context for when to use the tool (when linking an external model directory as a submodel). It does not explicitly name alternatives or provide when-not-to-use guidance, but the context is unambiguous enough for an agent to differentiate it from related tools.

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