Skip to main content
Glama

Fill or fix the texting registration

sms_registration_update
Idempotent

Saves fields of the toll-free texting registration as a draft (only while it is a draft or was rejected; never while the carriers review it). Send only the fields you are changing. Every fact must come from the person: ask for the legal name, entity type, address, contact and how people opt in; never guess or invent them, because carriers reject registrations that don't match official records. You may draft the use case summary, opt-in description and sample messages for the person to approve: each sample starts with the business name and ends "Reply STOP to opt out". The registration number (EIN, or SSN for a sole proprietor) cannot be set here: the person enters it in the dashboard. Returns the saved form (number masked) and the checklist. Nothing is sent to the carriers. 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": {
      "form": "<form>"
    },
    "name": "sms_registration_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
formYesOnly the fields to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by naming the state precondition, the required API key scope (account), the exact return payload (saved form with number masked plus checklist), and the fact that nothing reaches the carriers. It also discloses a hard limitation: the EIN/SSN cannot be set here and must be entered in the dashboard.

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?

Dense and front-loaded: the draft-only precondition and the return value arrive early, followed by the content rules. Some sentences carry several clauses, but each one contributes a constraint an agent would otherwise get wrong.

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?

Complete for a stateful mutation tool with a deeply nested single parameter and no output schema: preconditions, authorship rules, field-level exclusions, auth scope and return contents are all covered.

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

Parameters5/5

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

Schema coverage is already complete, but the description adds real meaning: every fact must come from the person and never be invented, and it may draft only the use case summary, opt-in description and sample messages, with the sample format rule (business name first, "Reply STOP to opt out" last). Those are content constraints the nested schema cannot express.

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: 'Saves fields of the toll-free texting registration as a draft.' The draft-versus-submit distinction separates it cleanly from sms_registration_submit without needing to inspect either schema.

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?

Explicit when-to-use conditions: only while the registration is a draft or was rejected, never during carrier review. It also says to send only changed fields and clarifies nothing is sent to carriers, which implicitly routes submission elsewhere. It doesn't name the submit sibling, which keeps it just short of a 5.

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