Skip to main content
Glama
hail

hail

Official

Read saved SMS application

get_sms_application
Read-onlyIdempotent

Retrieve saved answers and sender details for an existing SMS or number registration by verification ID. Recover kept documents and file names without creating a brand or filing a campaign.

Instructions

Read saved answers for an existing workspace registration.

    Returns private applicant fields, address and available sender information.
    An older application without saved answers returns 404.
    A number registration (``purpose="number"``) returns its kept answers,
    ``documents`` and the kept ``files`` by name (without their bytes) until
    ``kept_until``; ``resubmit_verification`` files it again from them.
    This read can recover an existing sender's details but creates no brand and files no campaign.
    Corrections retain the existing registration and its paid identity.

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": {
      "verification_id": "<verification_id>"
    },
    "name": "get_sms_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
verification_idYesID of the original registration, from ``list_verifications``: an SMS one, including one needing corrections, or a rejected number one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: private applicant fields are exposed, files are returned by name without bytes and only until kept_until, and older registrations 404. It also reassures that the call creates no brand and files no campaign and that corrections retain the existing paid identity. That is substantive mutation-safety context beyond what the annotations convey.

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?

Purpose is front-loaded and each following sentence carries a distinct fact (return contents, 404 case, number-registration specifics, non-mutation, correction behavior). The dense jargon ("kept answers," "kept_until," "paid identity") and inconsistent indentation make it slightly harder to scan than it needs to be.

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 with an output schema, the definition covers the meaningful failure mode (404), the special number-registration payload shape, and what side effects do not occur. Missing only peripheral details such as permission requirements or how long answers persist after kept_until, which are unlikely to change invocation decisions.

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 100% and the parameter description already explains that the ID comes from list_verifications and may be an SMS registration, one needing corrections, or a rejected number. The description adds framing about the target being an existing workspace registration and ties the ID to the returned kept answers/documents. Extra value is modest but real over an already complete schema.

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?

Opens with a specific verb+resource: "Read saved answers for an existing workspace registration," which tells an agent exactly what is fetched. It also distinguishes itself from mutation siblings by stating it "creates no brand and files no campaign" and that corrections are handled elsewhere. It stops short of naming amend/preview/resubmit explicitly, so the boundary is inferred 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?

Gives clear conditions for use and key edge cases: an older application with no saved answers yields 404, and a number registration returns kept answers with documents and files by name. It also signals the relationship to resubmit_verification. It does not explicitly say when to prefer amend_sms_application or preview_sms_application instead, so alternative-selection guidance is only implicit.

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