Skip to main content
Glama

mind_route

Read-onlyIdempotent

Selects the agent and model tier for classified file changes using capabilities and policy, and explains a file's language pack without authorizing or executing actions.

Instructions

Select an agent and model tier for classified changes using capabilities and policy. Use route to explain a file's language pack; this does not authorize or execute an action.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mind_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoFile paths to process

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.62.0
    • changedInput schema / properties / files / description
      Previous value: -"files to process"New value: +"File paths to process"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description reinforces this by clarifying the tool does not authorize or execute anything, which is genuine added context. It does not explain what a 'selection' produces, whether results are cached, or how policy conflicts are resolved.

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?

Two tightly packed sentences with the core purpose front-loaded and the sibling disambiguation second. No filler or repetition. Some compression cost is paid in vague phrasing like 'capabilities and policy.'

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?

There is no output schema, so the description carries the burden of explaining what a selection returns, and it only implies it. For a low-parameter, read-only routing tool this is adequate but leaves the agent guessing about the response shape and what 'classified changes' means in practice.

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?

There is a single optional 'files' parameter with 100% schema description coverage ('File paths to process'), so the schema carries the meaning. The description never mentions the files argument or what it does with them, adding nothing beyond the structured field. With coverage this high, baseline 3 is appropriate.

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?

States a specific verb and object: 'Select an agent and model tier for classified changes using capabilities and policy.' That is concrete enough to separate it from a pricer or classifier, and it explicitly contrasts itself with the sibling 'route' tool. The phrase 'classified changes' remains jargon the agent may not resolve without other context.

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?

Names an alternative ('Use route to explain a file's language pack') and states the negative boundary ('this does not authorize or execute an action'), which discourages misuse as an execution step. It stops short of saying when this tool should be chosen over mind_plan or mind_classify, but the routing guidance it does give is explicit.

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