Skip to main content
Glama

wait_for_sms

Polls a specified phone number until a new SMS arrives or the timeout expires, helping agents wait for incoming OTP or verification messages before continuing.

Instructions

Poll until a new SMS arrives on a free public number or timeout.

Args: phone: Phone number to watch. timeout: Max seconds to wait (default 120, max 300). poll_interval: Seconds between polls (default 10, min 5).

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": "wait_for_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes
timeoutNo
poll_intervalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 the important behavior that this call blocks and polls, plus bounded latency via timeout defaults and maxima. It does not say what happens on timeout (error vs empty result) or what 'new' is relative to, which is the key ambiguity for a poller.

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?

One front-loaded sentence states the behavior, followed by a compact Args block mapping each parameter to its meaning. No filler or restatement of the title, and the docstring-style layout is easy to scan.

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?

An output schema exists, so return values need not be explained. However, for a long-blocking polling tool the description omits the timeout failure mode and whether 'new' means since call start or since last read, which are exactly the details an agent needs to call this correctly.

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 description coverage is 0%, so the description has to carry parameter meaning, and it does: phone is the watched number, timeout is max seconds with default 120 and cap 300, poll_interval is seconds between polls with default 10 and floor 5. Constraints the schema omits entirely are supplied here; only per-parameter type detail is redundant.

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 states a specific verb and outcome: 'Poll until a new SMS arrives on a free public number or timeout.' That is concrete and distinguishable from a one-shot read. It does not name or contrast with siblings such as read_free_sms or check_paid_sms, so sibling differentiation is left implicit.

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 implied rather than stated: 'until a new SMS arrives' signals this is a blocking wait rather than a snapshot read, and 'free public number' implicitly scopes it away from paid numbers. There is no explicit when-to-use versus when-to-use-something-else guidance and no named alternative.

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