Skip to main content
Glama

Check the texting registration

sms_website_check
Idempotent

Runs every check the carriers care about on the saved registration, without submitting: missing or invalid form fields, and a live look at the person's website, privacy policy and terms (public, has the business name and address, and the privacy policy has the required sentence about mobile information). A few runs per 10 minutes. Use the results to help the person fix their form or their own site, then check again. Requires API key scope: account.

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_website_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=true, destructive=false; the description adds genuinely new context beyond them: that nothing is submitted, that it performs a live outbound fetch of the person's public website, privacy policy and terms, and that runs are rate limited to a few per 10 minutes. It also discloses the auth requirement (account-scoped API key). What it does not clarify is why a 'no submission' operation is marked readOnly=false, leaving a small ambiguity for an agent reasoning about side effects.

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?

Purpose is front-loaded in the first clause, followed by the check list, then operational constraints. The middle parenthetical is dense but every element is substantive (public, business name and address, required mobile-information sentence). No filler sentences.

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 zero-parameter, no-output-schema tool the description is close to complete: it covers what is inspected, the external-fetch behavior, the rate limit, and the auth scope. The one gap is that with no output schema, the agent gets only 'use the results' and no sense of whether failures come back as per-field findings or a pass/fail summary.

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 the schema baseline is 4. The description correctly signals that it operates on the 'saved registration' rather than accepting inputs, which tells the agent it must ensure registration data exists first.

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 ('runs every check ... on the saved registration') and pins the scope with 'without submitting', which distinguishes it from the sibling sms_registration_submit without either schema being opened. The parenthetical enumerates exactly what is validated (form fields, website, privacy policy, terms).

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?

Gives explicit workflow guidance: run the checks, use the results to help the person fix their form or site, then check again. The 'without submitting' phrase tells the agent this is the pre-flight tool rather than the submit path, plus a rate limit (a few runs per 10 minutes) and the required API key scope. It stops short of naming a sibling alternative explicitly, so a 4 rather than 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