Skip to main content
Glama

Hail Communication for AI

List verifications

list_verifications
Read-onlyIdempotent

List workspace carrier registrations, newest first.

    Items include IDs, applicant names and types, country, number type, purpose,
    state, rejection details, timestamps, confirmation method and SMS progress fields.
    States are awaiting_review, submitting, submitted, approved, rejected or cancelled.
    SMS steps include confirm_identity, filing, carrier_review, needs_information and runtime_setup.
    ``campaign_accepted`` alone does not authorize texting: runtime readiness and number attachment are also required.
    ``identity_confirmed`` can carry over to a later filing for the same person.
    ``waiting_for_credit`` means a carrier fee prevents the next step.
    ``credit_needed_cents`` is that registration's share of the additional credit needed,
    or null when it is not waiting. Shares across waiting registrations are additive.
    ``confirmation="code"`` identifies a carrier-texted confirmation code.
    Returns ``items`` or an error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_verifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoShow one kind of registration: ``number`` for registrations that let the user buy numbers, ``sms`` for US texting. Omitted: both.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
    • changedInput schema / properties / purpose / description
      Previous value: -"Only registrations for buying numbers (``number``) or only US texting registrations (``sms``). Omitted: both."New value: +"Show one kind of registration: ``number`` for registrations that let the user buy numbers, ``sms`` for US texting. Omitted: both."
  2. Changed2 schema fields changed
    • changedInput schema / properties / purpose / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "number",
      +      "sms"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / purpose / description
      Previous value: -"Only ``number`` or only ``sms`` registrations."New value: +"Only registrations for buying numbers (``number``) or only US texting registrations (``sms``). Omitted: both."
  3. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the state machine (awaiting_review through cancelled), the SMS step sequence, and several non-obvious domain rules: campaign_accepted does not authorize texting, identity_confirmed carries over to later filings, waiting_for_credit blocks progress, and credit_needed_cents shares are additive. These are exactly the semantics an agent cannot infer from annotations.

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 scope and ordering are front-loaded in the first sentence, followed by a compact field-and-rule inventory where each line carries distinct meaning. Phrasing is telegraphic in places (backticked identifiers, fragment sentences), which is dense but not padded.

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 read-only list tool with a full output schema and fully described parameters, this is close to complete: it covers ordering, item contents, state enum, and the confusing edge-case fields. The only real omission is routing versus sibling tools for single-item or status lookups.

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%, and the schema already explains that purpose=number buys numbers while purpose=sms is US texting. The description adds nothing about purpose or llm_model, so it sits at the baseline where the schema does all the work.

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?

"List workspace carrier registrations, newest first" names a specific verb (list), resource (carrier registrations), scope (workspace) and ordering. It is clearly distinct from get_verification or check_verification by implication, but it never names the single-item or status-check siblings to draw the contrast explicitly.

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 only implied by the tool name and the purpose filter description; the description itself gives no when-to-use or when-not-to-use guidance. It does not say to call get_verification for a single ID or check_verification for a status poll, leaving routing to the agent's 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