Skip to main content
Glama

Customer accepted

o2c_accept_quote
Destructive

Record customer acceptance and raise the sales order from the quoted lines. Prices copy across at acceptance and are then frozen on the order. If the list price moves tomorrow, this order keeps what was quoted — that is the whole reason the quote existed. The order arrives in draft: acceptance is the customer's act, confirmation is ours. Effects: quote.status -> accepted; draft order created with the quoted prices.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "o2c_accept_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
po_refNoThe customer's own PO number, if they gave one.
quote_idYesThe accepted quote. An existing quote id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: prices are copied and frozen at acceptance, the resulting order lands in draft, and the concrete effects are spelled out ('quote.status -> accepted; draft order created with the quoted prices'). The price-freezing rationale is exactly the kind of consequence an agent cannot infer from destructiveHint=false/true flags or a 2-param schema.

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?

Front-loads the action, then the price semantics, then the state effects — a sensible order. Slightly discursive in the middle ('that is the whole reason the quote existed'), but every clause carries meaning an agent needs.

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 non-idempotent, destructive mutation with no output schema, the description covers what changes and what gets created. It does not say what the call returns (e.g. the new draft order id), which an agent would want, but otherwise the picture is complete.

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 both quote_id and po_ref are already documented, and the description adds only the notion that the order is built from the quote's lines. That is a useful mental model but not parameter-level detail, so the baseline 3 applies.

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 compound verb-plus-resource action: 'Record customer acceptance and raise the sales order from the quoted lines.' It also implicitly separates itself from the confirmation step ('acceptance is the customer's act, confirmation is ours'), so an agent can distinguish this from o2c_confirm_order without opening either 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?

Gives a clear trigger condition (the customer has accepted a quote) and a clear boundary against the adjacent confirmation step. It does not name explicit exclusions or prerequisites such as whether the quote must be in a sent state, which keeps it short of a 5.

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.