Skip to main content
Glama

Update client

crunch_update_client
Idempotent

Updates an existing client's details by changing only the fields you provide while preserving all others; a new billing address replaces the entire address.

Instructions

Change a client's details. Only the fields you pass change; the rest are kept (a new billing_address replaces the whole address).

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": {
      "client_id": "<client_id>"
    },
    "name": "crunch_update_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name
noteNoInternal note about the customer
emailNoEmail address invoices are sent to
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
client_idYesClient (customer) ID (see crunch_list_clients)
billing_addressNoNew billing address (replaces the whole address)
payment_terms_daysNoDefault payment terms in days, for example 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses the key behavioral trait: it is a partial/patch update where unspecified fields are preserved, and that billing_address is replace-whole rather than merged. It does not say what happens on an unknown client_id or what the response contains, so not a 5.

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 short sentences, zero filler, with the patch semantics front-loaded before the address caveat. Every clause earns its place.

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 an 8-parameter mutation tool with a nested object and no output schema, the description covers the mutation model and the riskiest parameter behavior. Remaining gaps (return shape, error/precondition behavior) are minor given full schema coverage and annotations.

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 coverage is 100%, so every parameter including the nested address and dry_run is already documented; baseline is 3. The description's partial-update and whole-address-replacement notes restate what the schema descriptions already say, adding little new meaning.

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?

States a specific verb+resource ('Change a client's details'), which is clearly distinguishable from crunch_create_client and crunch_get_client. It stops short of naming any sibling or contrasting with a supplier/expense update, so it lands below a 5.

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

Usage Guidelines3/5

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

The description implies this is the mutation path for an existing client but gives no explicit 'use this when… / use X instead' guidance, no prerequisites (e.g., client must already exist), and no note that client_id comes from listing clients — that routing hint lives only in the schema.

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