Squish

Update account address

update_account_address

Destructive

Update the customer's billing address on file (Stripe + Salesforce). Two-step usage REQUIRED: (1) call with confirm:false to fetch the current address and preview the new one — describe both to the user in plain English; (2) ONLY after the user explicitly says yes, call with confirm:true to apply. NEVER call confirm:true without an explicit affirmative in the user's most recent message. If only some address fields are provided, the unspecified ones will be replaced with empty/null — make sure the user understands they're replacing the whole address, not patching it.

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": {
      "line1": "<line1>",
      "city": "<city>"
    },
    "name": "update_account_address"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City.
`line1`	Yes	Street line 1.
`line2`	No	Street line 2 (optional, e.g. apartment number).
`state`	No	State / province (e.g. "AZ").
`confirm`	No	false (default) returns preview; true applies. Pass true ONLY after explicit user confirmation.
`country`	No	Two-letter country code (e.g. "US"). Defaults to "US" if omitted.
`postal_code`	No	ZIP / postal code.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds crucial behavior beyond them: the preview/apply split, the exact confirmation gate, the fact that changes propagate to both Stripe and Salesforce, and that omitted fields are nulled rather than preserved. That last point is exactly the destructive side effect an agent needs disclosed.

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?

The write target is front-loaded, followed by the two-step procedure in numbered form, then the destructive caveat. Every sentence carries operational weight — no restatement of the name or filler.

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 7-parameter destructive mutation with no output schema, the description covers what triggers it, what it changes, where it changes it, and what the preview step returns. An agent has everything needed to call it safely and correctly.

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 per-field meanings are already documented and the baseline would be 3. The description earns above baseline by clarifying the non-obvious replace-not-patch semantics of the optional fields and the confirm flag's gating behavior, which the schema only hints at.

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?

The first sentence names a specific verb and resource ("Update the customer's billing address on file") and even identifies the downstream systems (Stripe + Salesforce), which distinguishes it from the sibling update_account_phone. An agent knows exactly what object this mutates 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 protocol: confirm:false to preview, confirm:true only after an explicit affirmative in the user's most recent message. It states both the required condition and a hard prohibition ("NEVER call confirm:true without..."), leaving nothing to inference.

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?