Simpler.Asia

quote_item_update

Edits a quote line's description, quantity, unit, price or discount, or moves it to another quote. expected_updated_at is required: the line's updated_at from your read; without it nothing is written and the refusal names the current value; a line changed since then answers CONFLICT. Refuses a line of a converted quote or a move onto one (CONFLICT: change its invoice instead). Bounds: unit_price_cents is integer CENTS, 0 or more; quantity 0.001 to 1,000,000 (3 decimals); discount_bps 0 to 10000; quantity × unit_price_cents at most 10,000,000,000. unit "" clears the unit. tax_code is the line's code under the document's tax_scheme, refused on a document without a scheme. NEXT: quote_read.

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>",
      "expected_updated_at": "<expected_updated_at>"
    },
    "name": "quote_item_update"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The quote_item id (quote_item_list shows them).
`unit`	No
`position`	No
`quantity`	No	How many, up to 3 decimals (1.5 hours → 1.5). A new line defaults to 1.
`quote_id`	No
`tax_code`	No
`description`	No
`discount_bps`	No	Optional line discount in basis points: 10% → 1000, none → 0. A discount is never a lower or negative price.
`unit_price_cents`	No
`expected_updated_at`	Yes	Required: the line's updated_at from your last read (quote_item_read, quote_item_list or the create answer). Left out, the call is refused and names the current value; a line changed since then returns CONFLICT with the current value and stays as it is.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing optimistic concurrency semantics: missing expected_updated_at causes a refusal that names the current value, and a stale line returns CONFLICT without writing. Also documents the converted-quote refusal, the cross-field ceiling (quantity × unit_price_cents ≤ 10,000,000,000), and that unit "" clears the field — none of which is derivable from the readOnly/destructive hints.

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?

Front-loads the operation, then the concurrency contract, then refusals, then numeric bounds, then the next step. Dense with no filler sentences; every clause carries a constraint or failure mode an agent must respect.

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 10-parameter mutation with no output schema, the description supplies the semantics that matter: precondition, conflict behavior, refusal conditions, unit conventions, and a verification follow-up. Only 'position' is left unexplained, which is minor relative to the rest.

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 only 40%, and the description compensates on the highest-risk params: unit_price_cents is integer CENTS ≥ 0, quantity 0.001–1,000,000 with 3 decimals, discount_bps 0–10000 with the 'discount is never a negative price' clarification, plus unit-clearing and tax_code scheme dependency. The remaining gap is that 'position' is never mentioned in the description and 'description'/'quote_id' only carry maxLength in the schema.

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?

Opens with a specific verb and resource ('Edits a quote line's...') and enumerates the editable facets (description, quantity, unit, price, discount, move to another quote), which cleanly separates it from quote_item_create/delete and quote_update. An agent can identify the target and scope 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 Guidelines4/5

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

States prerequisites (expected_updated_at from a prior read) and an explicit exclusion (refuses lines of converted quotes, and moves onto them, directing to change the invoice instead). It also names the follow-up ('NEXT: quote_read'). It does not explicitly name sibling alternatives such as quote_item_create or quote_update for adding vs. editing, so it stops just short of full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Simpler.Asia 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?