Skip to main content
Glama

Hail Communication for AI

Cancel a verification

cancel_verification
Destructive

Cancel an eligible carrier registration after explicit user authorization.

    Awaiting-review drafts are discarded; rejected registrations are dismissed.
    A rejected registration must be dismissed before a new one is submitted
    for the same country and number type.
    An approved US SMS registration can be cancelled: attached numbers lose US texting eligibility
    and its monthly fee ends after the current month.
    Some registrations have a minimum of three monthly fees even after early cancellation.
    Submitting or submitted registrations normally return 409; an accepted SMS campaign
    at runtime_setup is an exception.
    An SMS application at needs_information supports correction on its existing paid identity.
    Returns the cancelled 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>"
    },
    "name": "cancel_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
verification_idYesRegistration ID, from ``list_verifications`` or ``submit_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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description goes well past that: it discloses concrete consequences (attached numbers lose US texting eligibility, the monthly fee ends after the current month), a financial caveat (some registrations owe a minimum of three monthly fees even after early cancellation), and the 409 failure modes. It also states the return value ('the cancelled registration or an error'), which annotations 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?

The action and its authorization precondition are front-loaded, and each subsequent sentence carries a distinct state rule or consequence rather than filler. It is dense and slightly long, and the discarded-vs-dismissed distinction for awaiting-review versus rejected drafts could be phrased more crisply, but no sentence is redundant.

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, non-idempotent state-machine tool, the description covers eligibility, per-state outcomes, sequencing constraints, error behavior, side effects, and billing implications, and an output schema already handles return structure. An agent has enough to decide whether to call it and what to warn the user about beforehand.

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% for both parameters, so verification_id and llm_model are already fully documented as a registration ID sourced from list_verifications/submit_verification and an analytics-only model ID. The description adds no format, sourcing, or validation detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Cancel an eligible carrier registration') plus a precondition ('after explicit user authorization'). It is clearly distinguishable from siblings such as submit_verification, check_verification, or get_verification, which read/inspect or create registrations rather than tear them down.

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?

The description enumerates when cancellation applies per registration state: awaiting-review drafts are discarded, rejected registrations are dismissed, approved US SMS registrations can be cancelled, and submitting/submitted ones normally return 409 with a stated exception for an accepted SMS campaign at runtime_setup. It also gives a sequencing rule (a rejected registration must be dismissed before a new one is submitted for the same country and number type), which is exactly the kind of when-to-use guidance an agent needs.

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