Skip to main content
Glama

Hail Communication for AI

Confirm a verification with a code

confirm_verification

Confirm a registration using the code the carrier sent to the applicant.

    Incorrect or expired codes return a field error; the carrier can send a replacement after a day.
    Success advances the registration but does not guarantee immediate approval.
    A ``confirmation="reply"`` registration requires a direct reply to the carrier's text instead.
    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>",
      "code": "<code>"
    },
    "name": "confirm_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code the carrier texted to the applicant's mobile, exactly as the applicant read it out.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
verification_idYesID of a registration with ``confirmation="code"``, from ``list_verifications`` or ``get_verification``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"The 4 to 10 character code the carrier texted, as the applicant supplied it."New value: +"The code the carrier texted to the applicant's mobile, exactly as the applicant read it out."
    • addedInput schema / properties / code / maxLength
      Added value: +10
    • addedInput schema / properties / code / minLength
      Added value: +4
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, so the description's job is to add context — and it does: failure mode (field error for bad/expired codes), the one-day replacement window, the caveat that success advances but does not guarantee approval, and the alternate path for confirmation="reply". The only thin spot is not restating that repeating the call with the same code may not be safe (non-idempotent), which the annotations imply anyway.

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?

Four short sentences, each carrying distinct information, with the primary action front-loaded and failure/edge cases following. Slight redundancy in the trailing 'Returns the updated registration or an error' given a formal output schema exists.

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 state-advancing mutation with an output schema present, the description covers prerequisites (confirmation="code"), failure behavior, the reply-confirmation exclusion, and the limited meaning of success. Little is missing; the lingering gap is guidance on what to do after a field error (resend vs. wait for replacement).

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 100%, so the schema already documents code, verification_id, and llm_model in detail. The description adds only the constraint that the registration must have confirmation="code", which is largely repeated in the verification_id schema text. Baseline 3 is appropriate.

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 description states a specific verb and resource ('Confirm a registration using the code the carrier sent'), plus the mechanism (carrier-issued code to the applicant). This is clearly distinguishable from siblings like get_verification or check_verification, which retrieve rather than confirm state.

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?

It gives explicit conditions and an exclusion: 'Incorrect or expired codes return a field error; the carrier can send a replacement after a day' and 'A confirmation="reply" registration requires a direct reply to the carrier's text instead.' That rules out misuse on reply-type registrations. It doesn't name a sibling tool to use for the reply case, so it falls short of a full 5.

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