Skip to main content
Glama

Hail Communication for AI

Route a number to an agent

route_number
Idempotent

Set the saved agents that answer a number's calls and texts.

Omitted settings retain their current values. Returns the updated number record or an error.

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": {
      "number_id": "<number_id>"
    },
    "name": "route_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
clear_smsNo``true`` removes the agent that answers texts.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
number_idYesWorkspace phone number ID, from ``list_numbers`` or ``acquire_number``.
clear_voiceNo``true`` removes the agent that answers calls.
sms_agent_idNoAgent that answers incoming texts, from ``list_agents`` or ``create_agent``.
voice_agent_idNoAgent that answers incoming calls, from ``list_agents`` or ``create_agent``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, but the description adds genuinely new information: omitted fields retain current values (partial-update/PATCH semantics) and the call returns the updated number record or an error. What clear_voice/clear_sms actually destroy is left to the schema, which is a minor omission rather than a contradiction.

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?

Three short sentences, front-loaded with the core action; the omitted-settings note is a useful second beat. The final sentence about the return value is partly redundant given an output schema exists, so it is efficient but not maximally tight.

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?

Given the output schema and rich annotations, the description supplies the one thing structured fields don't convey — partial-update semantics and error-on-failure behavior. It could say more about when routing fails (e.g., invalid agent IDs) but is otherwise sufficient for an agent to invoke it correctly.

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%, including provenance hints for number_id, sms_agent_id, and voice_agent_id plus an explicit 'analytics only' note on llm_model, so the schema does the heavy lifting. The description adds nothing per-parameter beyond 'saved agents', hitting the baseline for high-coverage schemas.

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+resource: 'Set the saved agents that answer a number's calls and texts' names both the mutation (set/route) and the target (agents bound to a phone number), which clearly separates it from email-domain routing siblings. It stops short of naming any alternative tool explicitly, so it is clear but not differentiated by name.

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 only implied by the purpose statement — an agent can infer this is the tool to bind voice/SMS agents to an existing number. There is no explicit when-to-use vs. update_agent or acquire_number, no stated prerequisites (e.g., that the number and agents must already exist), and no exclusions.

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