Skip to main content
Glama

route_tool

Converts a natural language task into recommended tools and actionable next steps, detecting workflow patterns and suggesting activation order with example arguments.

Instructions

One-stop tool router: accepts a natural language task description, returns recommended tools and next actions. Automatically detects workflow patterns, recommends activation order, and provides example arguments. Use this instead of search_tools when you want guided tool discovery with actionable next steps.

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": {
      "task": "<task>"
    },
    "name": "route_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesNatural language description of the task you want to accomplish
contextNoOptional context hints for routing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the tool detects workflow patterns, recommends activation order, and returns example arguments — beyond a plain search — but never says whether it executes the task or can mutate state via the schema's autoActivate flag, nor anything about cost/latency or determinism.

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 tight sentences with the capability front-loaded and the sibling routing second. Only 'One-stop tool router' is slightly promotional filler, but it doubles as a useful category label.

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?

There is no output schema, so the description must describe returns — and it does, listing recommended tools, next actions, activation order, and example arguments. The remaining gap is behavioral: with zero annotations, the description should clarify whether recommendations are advisory only and whether autoActivate causes side effects.

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 description coverage is 100%, so all parameters including the nested context hints are already documented; the description only restates that it accepts a natural language task. Schema does the heavy lifting, so the 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 and resource — accepts a natural language task and returns recommended tools plus next actions — and names the concrete outputs (activation order, example arguments). An agent can distinguish it from search_tools / describe_tool / call_tool purely from this sentence.

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?

Explicitly routes the agent: 'Use this instead of search_tools when you want guided tool discovery with actionable next steps,' which gives both the alternative and the selecting condition. It stops short of stating the inverse (when plain search_tools is preferable, e.g. direct keyword lookup), so the guidance is clear but not fully two-sided.

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