Skip to main content
Glama

route

Select a candidate model for a text conversation; returns selected and probabilities without calling that model. Requires a Console API key.

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

Input Schema

NameRequiredDescriptionDefault
messagesYes
candidatesYes
selection_priorityNobalanced

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / cost_weight
      Removed value: -{
      -  "default": 0.3,
      -  "maximum": 1,
      -  "minimum": 0,
      -  "type": "number"
      -}
    • addedInput schema / properties / selection_priority
      Added value: +{
      +  "default": "balanced",
      +  "enum": [
      +    "quality",
      +    "balanced",
      +    "cheapest"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well on the highest-risk points: it explicitly states that no model is invoked, that the result is a selection plus probabilities, and that a Console API key is required. It stops short of describing determinism, error behavior, or what 'probabilities' represent.

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?

A single sentence, front-loaded with the action, followed by the return shape and the auth prerequisite. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with nested candidate objects, an enum that materially changes behavior, zero schema descriptions, and no output schema, the description leaves too much to inference. An agent cannot tell from the text how to shape candidates or what selection_priority does.

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%, so the description must compensate and largely does not. It never explains the selection_priority enum (quality/balanced/cheapest), the default of 'balanced', or the dual string-or-object form of candidates and the meaning of fields like price_in, price_out, context, and tags.

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?

The description names a specific verb and resource ('Select a candidate model for a text conversation') and adds a crucial scope boundary ('without calling that model'). It does not explicitly name its siblings decide or list_models, so an agent must infer the routing distinction from context rather than from stated differentiation.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling tools that presumably trigger a model call (decide) or enumerate options (list_models). The only implicit guidance is 'for a text conversation' and the API-key prerequisite.

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.

Resources