Skip to main content
Glama
hail

hail

Official

Correct an existing SMS application

amend_sms_application
DestructiveIdempotent

Correct an existing SMS registration at the needs_information step by submitting corrected fields, the existing address, and consent attestation; identity changes are rejected.

Instructions

Correct an existing SMS registration at the needs_information step.

    The address must be accurate; saved details can be reused when still correct.
    Identity changes are rejected. This operation does not create a replacement brand.
    Actual consent evidence is required.
    Limits are 100 fields and 64 KiB of combined fields and address. No documents are uploaded.
    A later campaign filing can incur the normal review fee.
    After a timeout, the existing registration can already reflect the correction.
    Returns the updated registration or an error.

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>",
      "fields": "<fields>",
      "attest_authorized": "<attest_authorized>"
    },
    "name": "amend_sms_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesComplete corrected answers that satisfy the current requirements; ``get_sms_application`` returns the saved ones.
addressNoThe sender's original address, as saved; ``get_sms_application`` returns it. Omitted: the correction is refused, because Hail cannot confirm the sender is unchanged.
verification_idYesID of the SMS registration at step ``needs_information``, from ``list_verifications``; the same paid application and identity.
attest_authorizedYes``true`` records that the applicant reviewed and approved these corrections.

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?

Goes well past the annotations by disclosing what will be rejected (identity changes), hard limits (100 fields, 64 KiB combined), that no documents are uploaded, that a later campaign filing may incur a review fee, and the important timeout caveat that the registration may already reflect the correction. This is exactly the mutation-risk context annotations alone cannot 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?

Front-loads purpose, then bullet-style constraint sentences that each carry distinct information (rejections, limits, fees, timeout). The telegraphic phrasing is efficient, though a couple of fragments could be grouped for faster scanning.

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?

Given a mutation tool with an output schema and nested address object, the description covers constraints, failure modes, cost side effects, and return behavior ('updated registration or an error'). Only authorization/prerequisite scoping (who may amend) is left implicit.

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%, so the baseline is 3, but the description adds real meaning: `fields` must be complete corrected answers, address must be accurate while correct saved details may be reused, and actual consent evidence is required for the attestation. A minor gap is that it never ties the 'no documents uploaded' rule explicitly to the fields payload.

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 ('Correct an existing SMS registration') and narrows scope to the needs_information step. It also rules out a nearby confusion ('does not create a replacement brand'), though it never names sibling tools like get_sms_application or preview_sms_application as the alternative path.

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?

Clearly frames the precondition (registration must be at needs_information, same paid application and identity) and gives exclusion rules: identity changes are rejected, no replacement brand is created. It lacks an explicit routing statement such as 'to start a new registration use X', so it is clear context rather than full when/when-not guidance.

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