Skip to main content
Glama

accounts_change_phone

DestructiveIdempotent

Initiate a phone number change for the current account by submitting a new phone with an optional challenge value.

Instructions

Initiate phone change PUT /accounts/me/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": {
      "body": "<body>"
    },
    "name": "accounts_change_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the risk profile is covered structurally. The description adds the meaningful behavioral signal that this only *initiates* the change rather than completing it, but says nothing about the challenge/verification mechanism, what gets destroyed (old phone number), or any rate limiting.

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?

The description is two short lines with no wasted prose and the operation is front-loaded. However, the brevity is under-specification rather than discipline, and the raw 'PUT /accounts/me/phone' line contributes little that an agent can act on.

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?

This is a destructive, open-world mutation with a nested input object, 0% schema description coverage, and no output schema. Given that complexity, the description leaves out the confirmation flow, the meaning of the challenge parameter, and any note about the effect on the existing phone number.

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% on a nested body object with a required 'phone' and an optional 'challenge' field. The description supplies no meaning for either field — notably it never explains where 'challenge' comes from or whether it is required on a first call — so it does not compensate for the coverage gap.

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 names a specific verb and resource ('Initiate phone change'), which distinguishes it from password-change siblings such as accounts_change_password and services_change_password. It stops short of distinguishing it from the paired confirmation tool (accounts_confirm_phone), so the two-step nature of the flow is not explicit.

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, no prerequisites, and no mention of the confirm step or of accounts_confirm_phone as the follow-up. The word 'Initiate' hints at a multi-step flow but the agent must infer that a second call is required.

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