Skip to main content
Glama

Text messaging setup

sms_setup_status
Read-onlyIdempotent

Returns where this workspace stands on texting: the status of its own toll-free number registration (none, draft, submitted, in_review, rejected or verified), the number, when it was submitted, the saved form (registration number masked), the checklist the business must meet, the latest website check results, and, after a rejection, a plain explanation with fix steps. Free and read only. Carriers only deliver marketing texts from a toll-free number verified under the business itself, which takes 1 to 2 weeks and sometimes up to a month: never promise a date. Use it to walk the person through the checklist item by item (privacy policy sentence, optional standalone opt-in, sample messages starting with the brand and ending "Reply STOP to opt out"). With the account scope you can fill and fix the form (sms_registration_update), run the checks (sms_website_check) and submit after a yes (sms_registration_submit); the registration number is always entered in the dashboard at setup_url. Text campaigns cannot be scheduled until status is verified. Requires API key scope: read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sms_setup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context beyond them: the 1-to-2-week (sometimes month-long) carrier verification, the explicit warning never to promise a date, and the required API key scope of read. It also tells the agent where the registration number is entered (dashboard at setup_url) rather than through this tool, which prevents a wrong action.

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 return payload, then the usage and domain constraints, which is the right order. It is dense and long, and a few clauses (the full checklist item list, the sample message wording) edge toward reference material rather than selection guidance, but none of it is filler.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the fields and their status values. For a domain as intricate as toll-free verification, it also covers timing, auth scope, and the correct next-tool path, so an agent can act without further context.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description could not add parameter meaning even in principle.

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 (returns where the workspace stands on texting) and then enumerates exactly what is returned: toll-free number registration status with its enum values, the number, submission date, masked registration number, checklist, website check results, and rejection explanation. This is clearly distinguishable from siblings like sms_registration_update or sms_website_check, which are named as separate actions.

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?

Explicit guidance on when to use it: to walk the person through the checklist item by item, and to read status before scheduling. It also names the downstream siblings (sms_registration_update, sms_website_check, sms_registration_submit) and the condition for each, plus the constraint that text campaigns cannot be scheduled until status is verified.

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