Skip to main content
Glama

Hail Communication for AI

Get a verification

get_verification
Read-onlyIdempotent

Read one carrier registration's current state and reported next step.

    The carrier state refreshes at most once per minute. Review can take business days.
    ``step="needs_information"`` means the existing SMS application needs corrections;
    its saved applicant details and paid identity remain attached to the same registration.
    An approved registration can make matching number offers ready for purchase.
    Rejections include ``rejection_reason``.
    ``waiting_for_credit`` indicates a fee awaiting payment.
    ``credit_needed_cents`` is this registration's share of the additional credit needed.
    Returns the registration record 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": "get_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

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: state refreshes at most once per minute, review can take business days, and it defines the semantics of needs_information, rejection_reason, waiting_for_credit and credit_needed_cents. It also states the return shape (registration record or an error).

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 core action is front-loaded in the first line, and the remaining lines are terse state glossary entries that each carry distinct meaning. The block of short ``code``-formatted sentences is slightly listy but no sentence is filler.

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 single-record read with an output schema present, the description covers freshness, latency expectations, the state vocabulary, and the error case, which is enough to call and interpret the tool. The only gap is how it relates to near-identical siblings such as check_verification, which would help an agent choose correctly.

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%, including the source of verification_id and the analytics-only note on llm_model, so the schema carries parameter meaning. The description adds nothing about parameter formats or side effects for those fields; its explanatory content concerns response states rather than inputs, which is the correct baseline-3 outcome.

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?

The first sentence gives a specific verb and resource: "Read one carrier registration's current state and reported next step." That is concrete and single-object scoped, and the parameter notes route the agent to list_verifications or submit_verification as ID sources. It stops short of distinguishing itself from close siblings like check_verification or get_verification_requirements.

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

Usage Guidelines3/5

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

Usage is implied by the state vocabulary (needs_information, waiting_for_credit, rejected), which tells an agent what questions this tool answers. However, there is no explicit when-to-use/when-not-to-use framing and no pointer to check_verification as the alternative for the same registration, so routing against siblings is left to inference.

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