Skip to main content
Glama

Prefill registration

prefill_registration
Destructive

Suggest a 10DLC registration from a business website: business and legal name, use case, description, opt-in, privacy and terms pages (ranked candidates), support email and draft example texts. Reads public pages only and changes nothing. The suggestions are guesses for the person to confirm.

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": {
      "website": "<website>"
    },
    "name": "prefill_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe business's website to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior1/5

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

The description states 'Reads public pages only and changes nothing', but the annotations declare readOnlyHint=false and destructiveHint=true. That is a direct conflict: an agent reading the prose would treat this as a harmless read and skip confirmation, while the structured metadata warns of a destructive, non-read-only operation. The description never clarifies whether a draft registration gets persisted or what such a write could overwrite, which is exactly the behavior an agent needs before calling it.

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?

Two sentences, front-loaded with the action and the produced fields, then the caveat that suggestions are guesses. Nearly every clause carries information; the one costly clause is the misleading 'changes nothing' claim, which is a correctness problem rather than padding.

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

Completeness2/5

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

The tool is simple (one required param) and the description does convey roughly what comes back (ranked candidate pages, draft example texts) despite no output schema. However, it leaves the most consequential fact unresolved: whether invoking it creates or overwrites any stored registration draft, which the destructive annotation implies it might.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'website' as a URI. The description adds only modest meaning beyond that ('from a business website', 'reads public pages'), without saying what happens with non-public, redirecting, or multi-page sites.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Suggest a 10DLC registration from a business website') and enumerates exactly what is suggested (business/legal name, use case, description, opt-in, privacy and terms pages, support email, draft example texts). That makes it clearly distinguishable from a real write tool such as create_registration or submit_registration, though no sibling 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 Guidelines3/5

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

Usage is implied by the framing: this is a prefill helper meant to be run before the person confirms and files a real registration. There is no explicit 'use this when...' statement, no statement about what to do if suggestions are wrong, and no named alternative for the confirm/submit step.

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.