Skip to main content
Glama

check_paid_sms

Check whether an SMS has arrived on a paid temporary number using its order ID, so you can confirm message delivery before retrieving OTPs.

Instructions

Check if an SMS arrived on a paid temporary number.

Args: order_id: Order ID from buy_temp_number.

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": {
      "order_id": "<order_id>"
    },
    "name": "check_paid_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the check is one-shot or blocking, whether repeated calls consume credits or sessions, or how the number is identified beyond the order; only the phrase 'if an SMS arrived' hints at a non-waiting check.

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 plus a short Args block; nothing is wasted. The Args heading is slightly redundant with the schema but harmless.

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 no explanation, and the single parameter is covered. What is missing for a polling-style SMS check is the behavioral contract: blocking versus non-blocking, retry cadence, and lifetime of the paid number.

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 description supplies the key missing meaning: order_id is the identifier returned by buy_temp_number. That provenance is genuinely useful, though no format or validity details are given.

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?

States a specific verb and resource ('Check if an SMS arrived on a paid temporary number'), and the 'paid' qualifier implicitly separates it from free-number siblings like read_free_sms. It stops short of naming an alternative directly.

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?

Implies usage through the prerequisite that order_id comes from buy_temp_number, which sketches the purchase-then-check workflow. It never says when to prefer this over wait_for_sms or whether to poll it, so guidance is only implied.

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