Skip to main content
Glama

Hail Communication for AI

List phone numbers

list_numbers
Read-onlyIdempotent

List dedicated workspace phone numbers, newest first.

    Items include ID, E.164 number, country, type, capabilities, provisioning state and assigned agents.
    Returns ``items`` and ``next_cursor``, or 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_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
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. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 200."New value: +"Number of items per page."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. First observed

TDQS

A3.5/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 covered. The description adds ordering ('newest first'), the field set of each item, and the paginated return shape with an error case — useful context, though it does not cover page-size limits or rate behavior.

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?

Two short paragraphs with the purpose and ordering front-loaded and no filler beyond a brief return-shape note. Every sentence carries information relevant to calling the tool.

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?

For a read-only paginated list with a full output schema, the description supplies purpose, ordering, item fields and the pagination contract. Filtering options are absent, but the tool exposes no filter parameters, so nothing essential 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?

Schema description coverage is 100% and the schema already documents limit, cursor and llm_model, including that next_cursor points to the next page. The description adds no parameter meaning beyond restating next_cursor, so the schema does the heavy lifting.

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 states a specific verb and resource ('List dedicated workspace phone numbers') and adds the ordering ('newest first'), so an agent knows exactly what this returns. It does not explicitly distinguish itself from siblings such as get_number or quote_numbers, which keeps it short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'dedicated workspace phone numbers'; there is no explicit statement of when to prefer this over get_number for a single lookup or quote_numbers for pricing. Adequate but leaves the agent to infer the selection criteria.

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