Skip to main content
Glama

read_free_sms

Retrieve recent SMS messages from a free public phone number without authentication so agents can inspect incoming codes and verification texts.

Instructions

Read recent SMS messages on a free public phone number. No auth needed.

Args: phone: Phone number (digits only, from list_free_sms_numbers).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "phone": "<phone>"
    },
    "name": "read_free_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: no auth needed. It leaves other behavior unstated — how far back 'recent' reaches, whether reading marks messages consumed, or any rate limits. Return values are covered by the output schema, which lowers the burden.

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?

Two short segments, front-loaded with the purpose and the auth fact, followed by a compact docstring-style arg note. Nothing is wasted and nothing essential is buried.

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 single-parameter read tool with an output schema, the definition covers purpose, auth posture, and argument sourcing. Only the message-window and any consumption semantics are missing, which are minor given the return shape is documented elsewhere.

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?

Schema coverage is 0%, so the description must compensate, and it does: it specifies digits-only formatting and names the sibling tool that supplies valid values. It does not state whether a country code is expected, which is a small residual ambiguity.

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 (read SMS messages) plus a scoping qualifier ('free public phone number'), which separates it from a paid-SMS sibling. It never names an alternative explicitly, so the differentiation is implied rather than stated.

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?

It supplies two practical conditions for use: no authentication is required, and the phone argument must come from list_free_sms_numbers, establishing a prerequisite step. It stops short of when-not guidance, such as routing to check_paid_sms or wait_for_sms when no messages exist yet.

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