relative-interpreter-mcp

Select model

select_model

Choose a model by ID to open it for the session, reset the scope to its root, and return the model's outline.

Instructions

Open a model for this session and reset the scope to its root. Returns its outline.

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": {
      "modelId": "<modelId>"
    },
    "name": "select_model"
  }
}

Input Schema

Name	Required	Description	Default
`modelId`	Yes	Model id from list_models.

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?

No annotations are provided, so the description carries the burden. It discloses the session-scoped open and scope reset side effects, and that it returns an outline. However, it does not mention permissions, session lifetime, or whether opening affects unsaved changes.

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 sentence that front-loads the action and key side effect, with no unnecessary words. It is concise and well-structured.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the core action, scope reset, and return value. It could add session semantics or prerequisites, but for this complexity it is largely complete.

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 covers 100% of the parameter descriptions, with modelId documented as 'Model id from list_models.' The description adds no additional parameter semantics, which is acceptable given complete schema coverage.

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 clearly states the tool opens a model for the session, resets the scope to its root, and returns its outline. This distinguishes it from siblings like get_model and enter_submodel by specifying a session-level open action and a scope reset.

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 usage when you need to open a model and reset navigation scope, but it does not explicitly mention when to prefer this over alternatives or any exclusions. There is no direct guidance on when not to use it.

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