Skip to main content
Glama

discover_routes

Read-onlyIdempotent

Finds filesystem route candidates with source paths and explicit inference confidence, enabling mapping of application routes for a specified project.

Instructions

Find filesystem route candidates with source paths and explicit inference confidence.

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": {
      "project": "<project>"
    },
    "name": "discover_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation, so the safety bar is covered. The description adds one genuinely useful behavioral fact — results are inferred candidates carrying an explicit confidence value rather than authoritative routes — but says nothing about scope, cost, or what happens with an unconfigured project.

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?

A single tight sentence with the action front-loaded and no filler. It is efficient, though brevity crosses into under-specification given the unexplained parameter.

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?

An output schema exists, so return values need not be explained, and the confidence framing is a helpful addition. However, for a discovery tool whose results drive downstream choices, the description gives no sense of what a 'route' is in this domain or what the search covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter 'project' is undocumented in both schema and description. The description never says what 'project' identifies or how it scopes the search, so it fails to compensate for the coverage gap.

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?

Specific verb ('Find') plus a named resource ('filesystem route candidates') and it also states what results carry (source paths, inference confidence). It does not explicitly differentiate itself from any sibling, but among a catalog of rendering/video tools its discovery role is discernible.

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

Usage Guidelines2/5

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

No statement of when this should be used, what problem it solves at the start of a workflow, or what alternative to reach for if it's not the right fit. The agent must infer usage entirely from the phrase 'route candidates'.

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