Skip to main content
Glama

Resend registration phone code

resend_registration_phone_code
Destructive

Text a new code to a sole proprietor's mobile for their registration. The old code stops working. At most 5 codes per submission, one a minute.

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>"
    },
    "name": "resend_registration_phone_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRegistration id (reg_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description goes meaningfully beyond the annotations by disclosing two behavioral traits: the previously issued code is invalidated ('the old code stops working') and hard rate limits of 5 codes per submission and one per minute. It does not say what happens when the limit is hit or whether SMS delivery failures are surfaced, but the invalidation and throttling details are exactly the kind of context an agent cannot get from destructiveHint alone.

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?

Three short sentences, front-loaded with the action and followed by the side effect and the limit. Every sentence carries information and nothing is redundant.

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 single-parameter, annotation-rich tool with no output schema, this is nearly complete: action, side effect, and rate limit are all present. Only the failure/exhaustion behavior and any user-facing error signaling are absent.

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?

With only one parameter at 100% schema description coverage, the schema already explains the 'id' (reg_...) field; the description merely echoes 'for their registration'. Baseline 3 applies because the schema is doing the documentation work.

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 gives a concrete verb and resource: it texts a new verification code to a sole proprietor's mobile as part of a registration. That is enough for an agent to tell it apart from 'enter_registration_phone_code' in practice, but no sibling is named or explicitly contrasted.

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 only implied: the word 'resend' plus 'the old code stops working' suggests this is used when a prior code is lost or expired. There is no explicit when-to-use versus when-not-to-use statement and no mention of the alternative entry tool, so the agent must infer the trigger 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.