Skip to main content
Glama

Hail Communication for AI

Fix and resubmit a verification

resubmit_verification
Destructive

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.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
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. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destruction and non-idempotency, and the description goes well beyond them: the 30-day retention window (kept_until), the rule that supplied arguments replace kept values while the rest are reused, the frozen fields (country, number type, subject type), the fact that a brand-new registration id is created and the rejected one dismissed, and the error shape ('problems') when nothing was sent.

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 a second paragraph carrying all the operational nuance. Every sentence delivers a distinct fact (retention window, replacement semantics, immutability, irreversibility, return/error shape) with no restatement of the name or title.

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 an eight-parameter, non-idempotent, destructive write with an output schema, the description covers the precondition, the mutation semantics, the immutable fields, the irreversibility and the failure mode. Nothing an agent needs in order to decide whether to call it, and what will happen if it does, 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 the general override/reuse rule that the per-field schema notes only state piecemeal: 'Each argument given replaces its kept value; the rest are reused.' It also flags attest_authorized as the gate — only true sends anything — which is the single most consequential parameter behavior.

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?

The opening sentence gives a specific verb and resource — refiling a rejected number registration — with the distinguishing qualifier 'with fixes, from what Hail kept.' That makes it immediately separable from submit_verification (new filing) and amend_sms_application (change to an existing application).

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?

The description sets clear preconditions: the verification must be rejected with 'resubmittable: true', and it points to get_sms_application for the kept answers and to submit_verification for the credit rules. It also gives a conditional escape hatch (quote_id 'for when the kept quote is gone (404)'). It stops short of an explicit 'use submit_verification instead when X' routing statement, which keeps it at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources