Skip to main content
Glama

Hail Communication for AI

List number search regions

list_number_regions
Read-onlyIdempotent

List US state and Canadian province codes supported by number searches.

    Returns ``regions`` containing ``country_code``, ``code`` and ``name``.
    These codes identify the optional region filter for a city search.
    An upstream failure returns an error.

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

Input Schema

NameRequiredDescriptionDefault
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds two genuinely new facts beyond annotations: the returned fields (country_code, code, name) and that an upstream failure surfaces as an error. Since an output schema already exists, the field enumeration is largely redundant, leaving the error note as the only real addition.

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?

Purpose is front-loaded in the first line, followed by return shape, downstream usage, and error behavior. The RST-style double-backtick formatting and the separate error sentence are slightly fussy for a trivial list tool, but nothing is meaningfully wasteful.

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 parameterless reference-list tool, the description covers purpose, what the codes are for, the returned fields, and failure behavior, while annotations and an output schema handle safety and return structure. Nothing an agent needs in order to call this correctly is missing.

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?

There is a single optional parameter (llm_model) with 100% schema description coverage, and the schema already states it is optional and recorded for analytics only. The description says nothing about it, but at full coverage the schema carries the burden, so the baseline 3 applies.

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 opens with a specific verb and resource: 'List US state and Canadian province codes supported by number searches.' It is unambiguous that this returns reference data (region codes) rather than phone numbers, which separates it from siblings like list_numbers. It stops short of an explicit contrast with any sibling, so a 4 rather than a 5.

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?

'These codes identify the optional region filter for a city search' tells the agent the downstream use case: fetch these first when a region filter is needed. There are no explicit exclusions or named alternatives, but for a static reference-list tool the context is sufficient.

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