Skip to main content
Glama

Update customer

update_customer
DestructiveIdempotent

Update an existing billing customer in your organization. Only the fields you provide are changed; everything else is left as-is (PATCH semantics). Discover ids with find_billing_work - never ask the user for an id.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "update_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew customer name (2-50 characters).
statusNoCustomer status. One of: Active, Inactive.
countryNoCustomer country.
currencyNoISO 4217 currency code (e.g. USD, EUR).
customer_idYesId of the customer to update (required). Must be a customer in your organization.
descriptionNoCustomer description (max 200 characters).
contact_nameNoPrimary contact person name.
contact_emailNoPrimary contact email address.
contact_phoneNoPrimary contact phone number.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the bar is lower, yet the description still adds real behavioral context: PATCH semantics means unlisted fields are preserved rather than cleared. That is precisely the nuance an agent needs to avoid clobbering a record, and it clarifies that 'destructive' applies to the fields being overwritten. It does not describe the response body, but no output schema exists and the description doesn't claim to.

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?

Two sentences, front-loaded with the action, then the PATCH guarantee, then the id-discovery rule. Zero filler and nothing repeated from the schema or annotations.

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 ten-parameter mutation tool with a fully documented schema and safety annotations, the definition covers what to send, how omissions behave, and how to obtain the required id. The only gap is the return shape, which is minor given there is no output schema to describe.

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, but the description earns a bump by explaining the semantics of omission across all ten optional properties: only what you send is applied. That meaning is not derivable from the per-field schema descriptions alone.

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 specific verb and resource ("Update an existing billing customer in your organization"), which the agent can immediately separate from create_customer, delete_customer, and the many non-customer update_* siblings. The scope word "billing customer" adds precision over a bare 'update customer'.

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

Usage Guidelines4/5

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

Gives a concrete prerequisite workflow: discover the id via find_billing_work and never prompt the user for one, which is the exact failure mode for an id-required update tool. It lacks an explicit 'use X instead for Y' exclusion, but the resource is narrow enough that alternatives are obvious from sibling names.

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.

Resources