Skip to main content
Glama
hail

hail

Official

List number search regions

list_number_regions
Read-onlyIdempotent

Lists supported US state and Canadian province codes to use as optional region filters in city number searches.

Instructions

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, and the description adds value beyond them by disclosing the error contract ('An upstream failure returns an error') and the shape of the returned regions collection.

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 with the purpose stated first, then the return shape, then the error case; nothing is filler, although restating the returned field names is partly redundant given the output schema.

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

Completeness3/5

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

For a zero-argument read tool with an output schema, the description covers purpose, usage context, and error behavior, but what remains missing is a note on ordering or stability of results and how many regions are returned.

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 tool takes no parameters, so schema coverage is not a concern and the baseline is 4; the description correctly adds no parameter guidance because none is needed.

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 and resource ('List US state and Canadian province codes') and scopes it to codes 'supported by number searches', which distinguishes it from the broader list_* siblings such as list_numbers or list_agents.

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?

Explains the intended use by tying the returned codes to 'the optional region filter for a city search', giving clear context for when to call it, but it stops short of explicitly sequencing it (for example, 'call before searching cities') or naming exclusions.

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