Skip to main content
Glama
hail

hail

Official

Fix and resubmit a verification

resubmit_verification
Destructive

File a rejected number registration again with corrections, replacing only changed fields or files and reusing Hail's kept answers; sends a new registration and dismisses the rejected one.

Instructions

File a rejected number registration again, with fixes, from what Hail kept.

    Hail keeps a number registration's answers and files for 30 days after
    submit (``kept_until``); ``get_sms_application`` returns the kept answers
    and file names. Each argument given replaces its kept value; the rest
    are reused. Country, number type and subject type stay as filed.

    Irreversible once sent: it files a new registration (a new ``id``) with
    the same credit rules as ``submit_verification``, and dismisses the
    rejected one. Returns the new registration, or an error with
    ``problems`` when nothing was sent.

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

Input Schema

NameRequiredDescriptionDefault
filesNoOnly the files that replace kept ones, in the ``submit_verification`` format. A slot not listed reuses its kept file.
fieldsNoAll form fields, replacing the kept ones. Null keeps them.
addressNoThe applicant's address. Give it when the requirements include one; otherwise leave it out.
quote_idNoA new offer, for when the kept quote is gone (404). Null reuses it.
documentsNoAll document slots ``{slot: {option, fields}}``, replacing the kept ones. Null keeps them.
verification_idYesID of a rejected number registration with ``resubmittable: true``, from ``list_verifications``.
attest_authorizedYesAttestation that the named person or business authorized this filing and supplied its details and files. Only ``true`` sends anything.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructive/openWorld/non-idempotent annotations: it discloses the 30-day retention window (kept_until), the merge semantics (each given argument replaces its kept value, the rest reused, country/number type/subject type frozen), that the action is irreversible and creates a new registration id while dismissing the rejected one, and that failures return an error with problems. This is exactly the mutation/irreversibility context an agent needs.

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?

Front-loaded with the action, then retention window, then merge rules, then irreversibility and return behavior — each sentence carries distinct information with no repetition of the schema. Formatting with backticked identifiers keeps it scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-branch mutation tool with 7 parameters and an output schema, the description covers preconditions, merge behavior, irreversibility, error shape, and cross-references the tools that supply verification_id and kept answers. Nothing an agent needs in order to call it safely is missing.

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: it establishes which parameters are replaceable versus immutable ('Country, number type and subject type stay as filed') and that unlisted file slots reuse kept files. It stops short of adding syntax detail for fields/documents beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('File a rejected number registration again, with fixes, from what Hail kept') and implicitly distinguishes itself from submit_verification by reference to shared credit rules and the rejected-registration precondition. An agent can tell this apart from submit_verification and get_verification without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the precondition clearly (a rejected registration with resubmittable: true, sourced from list_verifications) and covers conditional branches: supply address only when requirements call for one, supply quote_id when the kept quote is gone (404), and attest_authorized must be true to send. It also names submit_verification as the equivalent path for credit rules.

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