Skip to main content
Glama

Toll-free numbers to choose from

sms_numbers
Read-only

Lists toll-free numbers available for this workspace's first texting registration. Optional prefix (800, 833, 844, 855, 866, 877, 888). Read only: nothing is bought until sms_registration_submit. Requires API key scope: 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": "sms_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: that no purchase occurs until sms_registration_submit and that an API key scope of 'account' is required — both are things the annotations cannot express.

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 short sentences, front-loaded with the purpose, then the parameter, then the safety/scope caveat. No filler and nothing repeated.

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 one-optional-param read-only list tool with no output schema, the description covers purpose, the filter, the non-destructive guarantee, and the auth scope. It could note the shape of the returned list (e.g. number plus region), but nothing essential for correct invocation 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 0%, but the single parameter is an enum whose values the description restates (800, 833, 844, 855, 866, 877, 888) and labels 'optional'. It clarifies that the value is a number prefix, but adds little beyond the enum itself, so it sits at the baseline rather than compensating for the coverage gap.

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 ('Lists toll-free numbers') plus the scope ('available for this workspace's first texting registration'), which lets an agent distinguish it from sms_registration_submit and the other sms_* siblings without opening a 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?

The phrase 'first texting registration' and 'nothing is bought until sms_registration_submit' make the usage context and the follow-up action clear, effectively routing the agent to the submit tool. It stops short of an explicit 'do not use after registration is submitted' exclusion, so it is not a full 5.

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