Skip to main content
Glama

Enter registration phone code

enter_registration_phone_code
Destructive

A sole proprietor's registration: the code texted to their mobile after submitting (it lasts 24 hours). The right code sends the campaign to carrier review. The person reads it from their phone.

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": {
      "id": "<id>",
      "code": "<code>"
    },
    "name": "enter_registration_phone_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRegistration id (reg_...)
codeYesThe code from the text sent to the sole proprietor's mobile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and non-idempotent, and the description adds genuinely useful context beyond them: the code is valid for 24 hours and a correct code moves the campaign into carrier review. It does not address what a wrong or expired code does, nor what 'destructive' means in practice (presumably failed attempts or replacing a prior submission).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, but the final one ('The person reads it from their phone') is redundant trivia and the prose is evocative rather than front-loaded with the action. The key fact — a 24-hour expiry — is buried in a parenthetical.

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

Completeness3/5

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

For a destructive, non-idempotent two-parameter mutation, the definition never covers failure outcomes (wrong code, expired code), whether retries are safe given idempotentHint=false, or whether the registration must be in a specific state. The 24-hour validity and carrier-review outcome are the right kind of detail, but gaps remain.

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 coverage is 100% — both id (reg_...) and code are documented there. The description adds only the origin and lifetime of the code, which is context rather than parameter semantics; it adds little beyond the schema's own field descriptions. Baseline 3 is appropriate.

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

Purpose3/5

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

The description frames a scenario (a sole proprietor's code texted after submitting) rather than stating the action with a verb — it never explicitly says 'submits the code to verify/complete the registration.' An agent can infer the intent, but it must infer it, and the sibling resend_registration_phone_code is never contrasted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is implicit context (use it after the code has been texted), but no explicit when-to-use, no when-not-to-use, and no routing to resend_registration_phone_code when the code expires or never arrives — which is the obvious alternative.

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.