Skip to main content
Glama

accounts_confirm_phone

Destructive

Confirm a phone number change by submitting the required 4-digit verification code to complete the account phone update.

Instructions

Confirm change phone POST /accounts/me/phone/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": {
      "body": "<body>"
    },
    "name": "accounts_confirm_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare a non-idempotent, destructive, open-world write, so the description only needed to add context such as code expiry, failure modes, or what state changes on success. It adds none of that; the sole sentence is a restatement of the route. Nothing contradicts the annotations, but the description is behaviorally silent.

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?

Two terse lines with no wasted words and the action front-loaded, but the brevity comes from under-specification rather than disciplined editing. The raw HTTP route adds little for an agent that already has the tool name.

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 confirmation endpoint with no output schema, the definition covers the action and the routing. The annotation already signals it is a destructive, non-idempotent write, so no additional safety profile is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single nested body.code parameter, so the description needed to carry the meaning. It never mentions the code, where it comes from, or that it is a 4-character verification token; only the schema's minLength/maxLength=4 hints at that.

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?

"Confirm change phone" gives a verb and a resource, but the object of the confirmation (an SMS/OTP code for a pending phone change) is only inferable from the schema, not stated. It restates the endpoint path rather than explaining the action, and it does not distinguish itself from accounts_change_phone or accounts_security_confirmations_verify.

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 no when-to-use guidance: nothing says this must follow a prior phone-change request, that the code is short-lived, or when to prefer accounts_security_confirmations_verify instead. The two-step relationship with accounts_change_phone is left entirely to inference from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools