Skip to main content
Glama

Spoof Caller ID

SMS routes

list_sms_routes
Read-onlyIdempotent

SMS routes you can send on (route id + name). With a country, each route's price per message part there, cheapest first. Use the id as "route" in send_sms. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sms_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo2-letter ISO country code of the recipients, e.g. GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies; the description still adds useful behavior: the return shape, the cheapest-first ordering, and that the call is free of charge.

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?

Three short, front-loaded fragments with no filler; the return shape comes first, then the optional-country behavior, then the consumption hint.

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

Completeness5/5

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

For a single optional-parameter read tool with no output schema, the description still conveys return fields, ordering, and cost, leaving nothing an agent needs to call it correctly.

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?

Schema coverage is 100% and the country parameter is already documented with a pattern and example, but the description adds real meaning beyond it: supplying country switches the response to include price per message part for that destination and sorts by price.

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+resource ('SMS routes you can send on'), names the returned fields (route id + name), and links the id to the 'route' parameter of send_sms, so it is unambiguously distinguishable from siblings like get_prices or list_tts_voices.

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 tells the agent how to consume the result ('Use the id as "route" in send_sms') and explains that adding a country changes output to per-part pricing sorted cheapest first. It doesn't say when to prefer a different pricing tool, but the workflow guidance is clear.

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