Skip to main content
Glama

List numbers

list_numbers
Read-onlyIdempotent

List the phone numbers on your account.

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
qNoMatches digits of the number or its label
tagNoOnly numbers with this tag
modeNotest for sandbox numbers, live for real ones
poolNoPool id
customer_idNoOnly this customer's numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"test for sandbox numbers, live for real ones"
    • addedInput schema / properties / tag / description
      Added value: +"Only numbers with this tag"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds only the account-scoping context and does not describe pagination, ordering, or how filters behave.

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?

The description is a single front-loaded sentence with no wasted words. For a simple list operation, this is appropriately concise.

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?

The tool is low-complexity and its schema plus annotations cover much of the needed context. However, the description does not help route among similar listing/searching tools or mention that results can be filtered and may be paginated, leaving meaningful gaps.

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%, so all five optional parameters are already documented in the schema. The description adds no additional meaning about q, tag, mode, pool, or customer_id filtering.

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 gives a specific verb and resource: list the phone numbers on the account. This distinguishes it from searching available numbers, but it does not explicitly name or contrast sibling tools such as get_number or search_available_numbers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description offers no when-to-use guidance, prerequisites, or alternatives. It only states what the tool lists, leaving the agent to infer when to choose it over get_number, search_available_numbers, or list_number_pools.

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.