Skip to main content
Glama

Submit registration

submit_registration
Destructive

File a ready registration for carrier review, or resubmit one after a rejection. fees_acknowledged: true is the person's own acceptance of the carrier registration fees (separate from the per-text rate, a campaign billed for at least 3 months, non-refundable even if rejected); it is recorded with the time on the filed copy. The first submit for a business also carries the business attestation, signed by someone authorized to act for it, with the name they give. Both come from the person in this conversation. Our review can hold the filing for a person on our team; get the status afterwards.

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>",
      "fees_acknowledged": "<fees_acknowledged>"
    },
    "name": "submit_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRegistration id (reg_...)
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.
fees_acknowledgedYesMust be true. Confirms the registration fee terms above.

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 declare destructiveHint=true, openWorldHint=true and idempotentHint=false, but the description adds material context the annotations cannot: the fee is non-refundable even if rejected, the campaign is billed at least 3 months, the acceptance is stamped with a time on the filed copy, and the attestation is retained with API key, IP, user agent and legal-document date. It also warns that review can hold the filing and points the agent to fetch status afterwards. What is missing is any note on duplicate-submission or retry behavior for a non-idempotent, consequential call.

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 is front-loaded in the first clause and every sentence carries operative information; nothing is filler. The second sentence is a long chain of parentheticals that takes effort to parse, which keeps it from a 5.

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 consequential, nested-object tool with no output schema, the description covers the fee obligations, the attestation lifecycle, the review hold, and directs the agent to check status afterwards. It does not describe what a successful response contains or how to recover from a rejected filing beyond resubmitting, a minor gap given the pointer to status.

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, but the description is load-bearing here: the schema's fees_acknowledged text refers to "the terms above," and only the description defines those terms (non-refundable, 3-month minimum billing, recorded with time). It also clarifies that attestation is once per business and must come from the person in this conversation, adding scope meaning beyond the nested schema.

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?

"File a ready registration for carrier review, or resubmit one after a rejection" names a specific verb (file), resource (registration) and two distinct modes, which implicitly separates it from create_registration (drafting) in the sibling list. It stops short of naming the sibling it differs from, so the differentiation must be inferred from the word "ready."

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?

It states the two conditions that call for this tool (a ready registration, or a resubmission after rejection) and adds a conditional rule for the attestation: only the first submit for a business carries it. It does not state explicit exclusions or prerequisites such as "do not call before the registration is complete," leaving that 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.