Skip to main content
Glama

Sync or discard texting registration

spur_manage_texting_registration
Destructive

Refresh registration status from the carrier, or discard a draft registration after confirmation. Existing save/submit/pay/resend tools cover the rest of setup.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower, but the description still adds useful context: sync performs an external carrier roundtrip, and discard is scoped to a draft and gated on confirmation. It does not state whether a discarded draft can be recovered or what happens if the carrier refresh fails, which are the remaining behavioral gaps.

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?

Two sentences, both front-loaded with the actionable part: the actions first, the sibling routing second. Every clause earns its place and nothing is repeated from structured fields verbatim.

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 two-branch, destructive, external-calling tool with no output schema, the description covers both actions, the confirmation gate, and the boundary against the sibling registration tools. It stops short of describing sync's return value or the irreversibility of discard, which would complete the picture for a destructive operation.

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%, and the schema's oneOf branches with const values plus the detailed 'confirm' description already carry the full parameter burden. The description only restates 'after confirmation' at a high level and adds no new detail about the two action values or the boolean's semantics, so the baseline 3 applies.

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 pairs two specific verbs with their resources: refresh registration status from the carrier, and discard a draft registration. It also names the sibling tools (save/submit/pay/resend) that handle the remaining setup, so an agent can separate this tool's narrow remit from the surrounding registration family without opening any 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?

Usage routing is explicit for the negative case: save/submit/pay/resend cover the rest of setup, leaving this tool for status refresh and draft discard. The discard branch carries a precondition ('after confirmation'). What's missing is any positive trigger for sync, such as when status is stale or unknown, leaving the agent to infer that condition.

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