Squish

Update account phone

update_account_phone

Destructive

Update the phone number on the customer's account (Stripe + Salesforce). Two-step usage: (1) call with confirm:false to fetch the current phone and preview the change; (2) ONLY after the user says yes, call with confirm:true. NEVER call confirm:true without an explicit affirmative in the user's most recent message.

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": {
      "phone": "<phone>"
    },
    "name": "update_account_phone"
  }
}

Input Schema

Name	Required	Description	Default
`phone`	Yes	New phone number (any common format — Stripe normalizes).
`confirm`	No	false (default) returns preview; true applies. Pass true ONLY after explicit user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds real context: the write propagates to two external systems and confirm:false returns the current phone as a preview. It does not cover failure semantics (e.g. Stripe succeeding while Salesforce fails), which is the main remaining gap for a cross-system mutation.

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?

Front-loaded with the action and systems affected, then the procedural rule. The confirm:true warning is restated in both the description and the parameter schema, which is mild redundancy but defensible for a destructive write.

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

Completeness5/5

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

For a two-parameter, no-output-schema destructive tool, the description covers what it does, where it writes, what the preview returns, and the confirmation gate an agent must honor. Nothing needed to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the ordering contract between the two parameters (confirm:false first to preview, true only after user assent) rather than just restating their types. It does not add phone-format detail, but the schema already handles that.

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

Purpose5/5

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

States a concrete verb+resource (update phone number on the customer's account) and names the downstream systems touched (Stripe + Salesforce), which no sibling does. An agent can distinguish it from update_account_address without opening the schema.

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

Usage Guidelines5/5

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

The description prescribes an explicit two-step sequence with the exact condition that selects each step, plus a hard exclusion ('NEVER call confirm:true without an explicit affirmative in the user's most recent message'). This is the strongest form of when/when-not guidance.

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

All Squish tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?