Skip to main content
Glama

List toll free verifications

list_toll_free_verifications
Read-onlyIdempotent

List toll-free verifications and their status (draft, in_review with us, submitted to the carriers, verified, rejected). A toll-free number texts the public only once verified.

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_toll_free_verifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25, max 100)
cursorNonext_cursor from the previous page
statusNoOnly verifications with this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 25, max 100)"
    • addedInput schema / properties / status / description
      Added value: +"Only verifications with this status"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful domain context about verification statuses and the business rule that texting the public requires verification, but it omits pagination behavior and does not describe the returned verification objects.

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?

The description is two sentences with no wasted words, and the core purpose and status list are front-loaded. The second sentence earns its place by explaining why verification status matters.

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 low-complexity list tool with full schema coverage and rich annotations, this is nearly complete for selection and invocation. The main gap is that no output schema exists and the description does not outline the shape of a returned verification, though pagination is covered by the schema.

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 limit, cursor, and status. The description reinforces the status values with lifecycle labels such as 'in_review with us' and 'submitted to the carriers', but adds no guidance for limit or cursor beyond what the schema provides.

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: 'List toll-free verifications and their status'. It also names the lifecycle statuses, which clearly distinguishes this list operation from the sibling get_toll_free_verification tool.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as get_toll_free_verification, nor are there any exclusions or prerequisites. The second sentence gives domain context about when a toll-free number can text the public, but it does not help the agent choose between tools.

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.