Skip to main content
Glama

List Sending Numbers

list_sending_numbers
Read-only

List the phone numbers this account can send text messages from, whether each can send right now, and which one send_message uses by default (isDefault). Pass a number's number as send_message's from to send from it instead. A new account usually has a main toll-free number awaiting carrier approval plus a temporary trial number that only allows a small number of messages; once the main number is approved it becomes the default.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
statusYes
contextNoAdditional context about why the call was blocked
numbersNo
successYes
errorCodeNoMachine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures.
nextStepsNoExplicit recovery guidance for the calling agent
statusTextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds meaningful domain behavior — that the default sender is flagged via isDefault and that a new account typically has a toll-free number pending carrier approval plus a trial number capped at a small message volume. That approval/lifecycle context helps an agent interpret a 'cannot send yet' result rather than treating it as an error.

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 sentences, front-loaded with purpose and return contents, followed by the cross-tool usage hint and the account-lifecycle caveat. No filler; every sentence changes how an agent would act on the result.

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?

Complete for a zero-parameter read tool with an output schema and read-only annotation — the return shape is documented structurally, and the description supplies the interpretive context the schema cannot. Only a note about empty results (no numbers provisioned) is arguably 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 no input parameters, so the baseline is 4. The description instead clarifies output field semantics (`number`, `isDefault`) that the agent will reuse when calling send_message.

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 phone numbers this account can send text messages from') and immediately defines what each entry conveys: whether it can send right now and whether it is the default. An agent can distinguish this read-only listing tool from send_message without consulting the schema.

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?

Gives a concrete use path by naming the sibling send_message and explaining that a number's `number` value is passed as send_message's `from` to send from that number. It stops short of stating when not to call it (e.g., a single-number lookup or when the sender is already configured), so guidance is strong but not exhaustive.

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