Skip to main content
Glama

Update supplier

crunch_update_supplier
Idempotent

Update supplier details or archive/restore a supplier by passing only the fields to change.

Instructions

Change a supplier's details, or archive/restore it. Only the fields you pass change.

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": {
      "supplier_id": "<supplier_id>"
    },
    "name": "crunch_update_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
countryNoCountry code, for example GB (see crunch_list_countries)
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
archivedNoArchive (true) or restore (false) the supplier
supplier_idYesSupplier ID (see crunch_list_suppliers)
company_nameNoNew name
contact_nameNoContact at the supplier
expense_typeNoDefault expense type for this supplier's expenses, for example TELEPHONE (see crunch_list_expense_types)
vat_registration_numberNoThe supplier's VAT number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds genuine behavioral value by clarifying that unspecified fields are left untouched, but it says nothing about whether archiving hides the supplier from other listings, what permissions are needed, or that dry_run can preview the diff — the last being the most consequential omission for a mutation tool.

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 core mutation and the partial-update rule both front-loaded. Nothing is repeated from the schema or the title.

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 9-parameter mutation tool with a nested passthrough object and no output schema, the description plus rich per-parameter schema text covers nearly everything an agent needs. The remaining gap is that the dry_run preview capability and archive side effects are only implicit or schema-level rather than called out as behavior.

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 baseline is 3; the description earns one extra point because 'only the fields you pass change' explains the semantics of omitting optional parameters, which the schema cannot express on its own. It still adds nothing about the 'extra' passthrough object or the archived flag's effect, both of which the schema already documents.

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 and resource ('Change a supplier's details') and additionally discloses that the tool handles archive/restore, which an agent would not otherwise expect from an 'update' name. It reads clearly against 'create'/'get' siblings by verb alone, though it never names an alternative tool to sharpen the boundary.

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?

'Only the fields you pass change' implies a partial-update usage pattern and signals that callers should send a minimal payload, which is useful guidance. However, there is no explicit when-to-use/when-not statement, no mention of when to prefer create vs update, and no prerequisites (e.g. that a supplier must already exist and supplier_id is required).

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