Skip to main content
Glama

Submit toll free verification

submit_toll_free_verification
Destructive

Send a draft, or a rejected form that was fixed, for review: it becomes in_review, we check it (usually within minutes) and then file it with the carriers (usually 4 to 5 business days). The first form for a business carries the business attestation, signed by someone authorized to act for it, with the name they give in this conversation. Answers with problems while anything the carriers require is missing. No fee.

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": {
      "id": "<id>"
    },
    "name": "submit_toll_free_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesToll-free verification id (tfv_...)
attestationNoSigned by someone authorized to act for the business, once per business: that they are authorized, that the details match the business's IRS records, and that the business will text only people who agreed to it and will follow the Messaging Policy. Kept as signed, with the exact wording, who sent it (the API key), the IP address, the user agent and the date of our legal documents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, open-world, destructive operation; the description supplies the substance behind that: the state becomes in_review, review is usually minutes, filing takes 4-5 business days, and there is no fee. It also discloses the attestation requirement and its evidentiary recording (signer, API key, IP, user agent, legal doc date). It stops short of saying whether a submission can be withdrawn or how failures after acceptance are handled.

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?

Front-loaded with the action and the state transition, then timing, attestation, error behavior and fee, each in a compact clause. A few sentences are dense and slightly run-on (notably the attestation sentence), but there is almost no wasted text.

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?

With 100% schema coverage, a nested attestation object and no output schema, the description covers the lifecycle gap that the schema cannot: what triggers submission, how long review and filing take, cost, and error behavior. The main residual gap is irreversibility of the carrier filing, which matters given destructiveHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining that the attestation is required on the first form for a business and is signed by someone authorized using the name given in this conversation, implying it is not needed on later submissions. The id parameter is left to the schema, which is reasonable given its full description.

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?

Uses a specific verb with a precise scope: sending a draft or a fixed rejected form for review, with the resulting state (in_review), the check, and the carrier filing spelled out. An agent can tell what outcome to expect. It does not name a sibling (create_toll_free_verification, update_toll_free_verification) to sharpen the boundary, so the highest score is not warranted.

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?

The opening clause establishes preconditions clearly – the form must be a draft or a rejected form that was fixed – which implicitly excludes other states. It also notes the tool errors while carrier-required information is missing, giving a usable readiness check. There is no explicit statement of when not to use it or which sibling to choose instead.

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.