Skip to main content
Glama

Update customer

update_customer
Destructive

Rename a customer or change its external_id or metadata.

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": "update_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCustomer id
nameNoThe customer's name
metadataNoUp to 50 string values
external_idNoYour id for them; unique per account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"The customer's name"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false; the description adds nothing to explain what is destructive or irreversible here. It never states that this is a partial update (omitted fields untouched), what happens on an external_id uniqueness collision, or that renaming may break references elsewhere.

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?

A single front-loaded sentence with no filler; the mutable-field list comes immediately after the verb. It is efficient, though the brevity is also the source of its behavioral gaps.

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?

For a destructive, non-idempotent mutation with a nested metadata object and no output schema, the description is far too thin: it explains neither consequences nor partial-update behavior nor error conditions. The schema covers the parameters, but nothing covers the risk profile.

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?

Schema description coverage is 100%, so all four parameters including the required id and the nested metadata constraints are documented in the schema. The description only echoes the field names without adding format, conflict, or merge semantics, so baseline 3 applies.

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 ('Rename a customer') and enumerates the mutable fields (name, external_id, metadata), which cleanly separates it from create_customer, delete_customer, and get_customer. It does not explicitly contrast with update_contact, but the resource boundary is obvious from the name.

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 guidance on when to use this versus alternatives such as update_contact, upsert_contact, or bulk_update_contacts, nor any stated prerequisites (permissions, whether the customer must exist). The agent must infer all of that.

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.