relative-interpreter-mcp

Import model

import_model

Import a model from exported Relative JSON and select it for use.

Instructions

Create a model from exported Relative JSON and select 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": {
      "json": "<json>"
    },
    "name": "import_model"
  }
}

Input Schema

Name	Required	Description	Default
`json`	Yes	A full Relative model JSON document.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Aug 11, 2026

TDQS

A3.8/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. It discloses that the tool creates and selects a model, which implies mutation and side effects. However, it does not mention failure behavior, permissions, or whether it overwrites existing models, though the simplicity of the operation makes this less critical.

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 sentence that directly states the purpose and expected outcome. No filler words or redundant information, making it optimally sized and front-loaded.

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 and no output schema, the description adequately covers the main context: what the tool does (create from JSON), the input source (exported Relative JSON), and the result (selection). It could mention whether the operation is destructive, but given the simplicity, the current level is sufficient.

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 schema already provides a full description for the only parameter ('A full Relative model JSON document') with 100% coverage. The description adds a minor nuance by saying 'exported', implying the JSON comes from an export function, but this is not a significant addition over the schema.

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 specifies 'Create a model from exported Relative JSON and select it', which clearly states the action (create), resource (model), and input source (exported Relative JSON). It also distinguishes from siblings like create_model (which likely creates a blank model) and select_model (which only selects) by including both creation and selection.

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

Usage Guidelines3/5

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

The description implies the use case (importing an exported Relative JSON document) but does not explicitly state when to use this tool instead of alternatives such as create_model or select_model. It provides context but lacks explicit exclusions or alternative guidance.

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