Skip to main content
Glama

Route task

route_task
Read-onlyIdempotent

Choose the least-burden eligible route for a task. Hard constraints include quality, reliability, locality, capabilities, context, cost, latency, and energy. Optional baselines quantify predicted savings. Explicit allow_defer/value/urgency fields may produce a no-work decision; no result is then claimed. Returns a hash-bound decision receipt.

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_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task with its constraints: quality, cost, latency, energy and so on.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
    • addedInput schema / properties / task / description
      Added value: +"The task with its constraints: quality, cost, latency, energy and so on."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnly/idempotent/non-destructive annotations, the description discloses two behaviors an agent could not otherwise know: a no-work decision is possible and 'no result is then claimed' (so absence of output is not an error), and the response is a hash-bound receipt. It does not explain how conflicts among hard constraints are resolved or what the receipt binds to, which keeps it below a 5.

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?

Five short sentences, front-loaded with the core action, with zero filler and each clause carrying a distinct fact (constraints, baselines, no-work case, return type). Dense nominal phrasing ('least-burden eligible route') costs some readability but no sentence is wasted.

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?

An output schema exists, so not explaining the receipt's shape is fine, and the description covers the notable failure mode (no-work decision) plus the constraint vocabulary for the untyped task object. The remaining gap is that it never explains how an agent should encode or weight constraints inside that free-form object.

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

Parameters4/5

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

The schema covers both top-level parameters at 100%, but the 'task' object is free-form (additionalProperties: true), so the description carries real weight by enumerating the constraint axes (quality, reliability, locality, capabilities, context, cost, latency, energy) and the optional allow_defer/value/urgency fields that can trigger a no-work decision. That meaning is not derivable from the schema alone.

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 resource ('Choose the least-burden eligible route for a task') plus the constraint dimensions considered and the output artifact ('hash-bound decision receipt'). An agent can tell this is the decision-making tool rather than the recording tool (record_route_outcome) or the planning tool (best_next_steps), though no sibling is named explicitly.

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?

Usage is implied rather than stated: you call it when you need a route chosen under hard constraints, and the mention of allow_defer/value/urgency hints at when a deferral is appropriate. There is no explicit 'use this instead of X when Y' routing and no stated prerequisites, so the agent must infer selection from the sibling names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.