Skip to main content
Glama

route

Read-onlyIdempotent

Resolve a file path to its language pack and return the governing rule, evidence, guide, manifest, and precedence, making clear which checks apply.

Instructions

Explain how a file path resolves to a language pack: returns the rule, evidence, guide, manifest and precedence. Use port for the full pre-edit brief; mind_route selects an agent instead. Successful structured results include the command record and exit code.

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": {
      "path": "<path>"
    },
    "name": "route"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExisting path, absolute or relative to the client directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.63.0
    • changedInput schema / properties / path / description
      Previous value: -"path"New value: +"Existing path, absolute or relative to the client directory."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so safety is covered. The description adds that results are structured and include a command record and exit code, hinting the output wraps an executed command, but it does not say what happens on a missing or invalid path. That remaining gap keeps it at 3.

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?

Two tight sentences: the first defines what is returned, the second routes to alternatives, and a third covers result shape. Front-loaded with the primary outcome and no 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?

No output schema exists, and the description lists the result components plus the command record and exit code, which is enough to anticipate the response. Minor gap: no mention of failure behavior for paths that don't resolve to a pack.

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 coverage is 100% and the single path parameter is already documented as an existing path, absolute or relative. The description adds no format, normalization, or relative-base meaning beyond that, so baseline 3 applies.

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?

States a specific verb (resolve/explain) and resource (file path → language pack resolution), and enumerates the returned components: rule, evidence, guide, manifest, precedence. It also explicitly distinguishes itself from two siblings (port for the full pre-edit brief, mind_route for agent selection).

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?

Gives clear routing: use port when you need the full pre-edit brief, use mind_route to select an agent, otherwise this tool explains the resolution. It lacks explicit when-not conditions such as non-existent paths or why one would inspect resolution at all.

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