Skip to main content
Glama

Submit the texting registration

sms_registration_submit

Sends the registration to the carriers for review. The first time it also buys the chosen toll-free number (phone_number from sms_numbers, included in the person's add-on). After a rejection it resubmits the same request with the fixes. Only after the person reviewed the form (sms_setup_status) and said yes: needs confirm: true. Every check runs again first; if one fails, nothing is sent or bought. Current API builds answer submit_in_dashboard: the submit needs the person's EIN or SSN, which Hollerpost sends straight to the carriers and does not keep, so the person submits in the dashboard (setup_url, Settings, Text messaging); pass that on. Review takes 1 to 2 weeks, sometimes a month; never promise a date. The person gets an email when the status changes. Requires API key scope: account.

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": {
      "confirm": "<confirm>"
    },
    "name": "sms_registration_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue: the person approved submitting.
phone_numberNoFirst submission only: the toll-free number the person picked, E.164 (+18335550100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: discloses the one-time phone-number purchase, the all-or-nothing check behavior ('if one fails, nothing is sent or bought'), the EIN/SSN handling that prevents in-API submission on current builds, a 1-2 week (sometimes month) turnaround, and email notification on status change. It even states the required API key scope (account), which annotations never convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded, but the body is a dense run-on paragraph mixing side effects, preconditions, fallback routing, and SLA timing. The sentence 'Current API builds answer submit_in_dashboard: ...' is garbled and forces the agent to re-parse it to extract the actual condition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent, externally-visible, open-world mutation with no output schema, the description covers everything an agent needs: approval gate, cost side effect, failure atomicity, turnaround expectations, and the dashboard fallback. Nothing material about calling it correctly is missing.

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 coverage is 100%, so both parameters already document themselves, including the E.164 pattern and 'First submission only'. The description adds modest context — that phone_number comes from sms_numbers and is part of the person's add-on, and that confirm:true encodes the person's verbal approval — but most of what it says about the parameters duplicates the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource — 'Sends the registration to the carriers for review' — and immediately distinguishes the two execution modes (first submission buys the toll-free number; after a rejection it resubmits with fixes). An agent knows this is the terminal submit step, not a draft or settings update, and the side effect on sms_numbers is named explicitly.

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

Usage Guidelines5/5

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

Gives an explicit precondition chain ('Only after the person reviewed the form (sms_setup_status) and said yes: needs confirm: true') and names the sibling to check first. It also routes the agent elsewhere when submission is impossible in this API build (submit_in_dashboard, setup_url, Settings, Text messaging), which is a genuine when-not-to-use path.

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