Skip to main content
Glama

list_free_sms_numbers

Lists available free public phone numbers for receiving SMS without authentication, helping agents find shared numbers to check incoming messages.

Instructions

List available free public phone numbers for receiving SMS. No auth needed.

Returns: JSON with available phone numbers from receive-sms-free.cc. These are shared public numbers — anyone can read messages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose meaningful traits: no authentication required, the upstream source (receive-sms-free.cc), and the critical caveat that numbers are shared public and readable by anyone. It omits operational traits such as number lifetime, volatility of the list, freshness, or any rate limiting.

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 blocks, front-loaded with the purpose and the auth fact, then the privacy warning. The 'Returns:' block partially duplicates the existing output schema, but the shared-number warning inside it earns its place.

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 zero-parameter tool with an output schema and no annotations, the definition covers the essentials an agent needs: no auth, what comes back, and the shared-public nature of the numbers. Number lifetime and list volatility are the only notable gaps.

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 parameters, so the baseline applies. Nothing is needed beyond confirming the call is unfiltered and unfiltered it is.

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 available free public phone numbers for receiving SMS') and the word 'free' implicitly contrasts with paid alternatives like check_paid_sms and buy_temp_number in the sibling set. It stops short of naming a specific sibling to route against, but the scope is unambiguous.

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: an agent can infer this is the entry point for finding a number before reading messages, and 'No auth needed' removes a setup question. There is no explicit when-to-use/when-not guidance or named alternative for paid or dedicated numbers.

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