hail

Official

by hail-hq

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

List number search regions

list_number_regions

Read-onlyIdempotent

List the US state and Canadian province codes that quote_numbers accepts as region (optional, with city).

Instructions

List the US state and Canadian province codes that quote_numbers accepts as region (optional, with city).

    Returns ``{"regions": [{"country_code", "code", "name"}]}``, such as
    ``{"country_code": "US", "code": "AZ", "name": "Arizona"}``, or
    ``{"error": "<message>"}``.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.29.0Oct 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the exact response envelope ({"regions": [...]}) and the {"error": "<message>"} failure shape, which is real behavioral context an agent cannot get from annotations.

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 compact sentences, front-loaded with what is listed and immediately followed by the return shape and a concrete example. Nothing is redundant and no sentence could be dropped without losing information.

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 zero-parameter read-only lookup, the description covers purpose, linkage to quote_numbers, return structure, and the error case. With an output schema present it need not do more, and nothing required for correct invocation is missing.

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 zero parameters, so the baseline is 4. The description still adds meaning by explaining how the returned `code` values are consumed as the `region` argument of quote_numbers, which helps the agent use the output correctly.

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 the region codes that quote_numbers accepts as `region`) and ties the resource to a named sibling, so it is clearly not one of the other list_* tools. The example entry makes the granularity unambiguous: state/province codes, not phone numbers.

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?

The reference to quote_numbers accepting these codes as `region` (optionally with `city`) gives a clear implicit context: call this before filtering a quote by region. It does not spell out an explicit 'use this instead of X' rule or state that no parameters are needed, but the surrounding workflow is easy to infer.

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