Skip to main content
Glama

update_sales_draft

Replace the editable contents of a quote or invoice draft using its current revision.

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>",
      "revision": "<revision>",
      "snapshot": "<snapshot>"
    },
    "name": "update_sales_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes
snapshotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context by signaling full-replacement semantics ('Replace' the editable contents) and by tying the call to the draft's current revision, but it omits what a stale revision returns and which fields are outside the 'editable' set.

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?

A single tight sentence that front-loads the mutation verb and ends with the key constraint. There is no filler, though it is arguably too terse for a tool with a large nested payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity write tool with a deeply nested 3-parameter schema, no output schema, and no parameter descriptions. The description explains neither conflict handling on revision mismatch, nor what the response contains, nor the scope of 'editable', so an agent cannot confidently call it without trial and error.

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 description coverage is 0% across three required parameters, including a deep nested snapshot object, so the input schema alone is weak. The description compensates only for 'revision' (must be the draft's current revision) and loosely for 'snapshot' ('editable contents'), leaving the required nested fields, item limits and mutually exclusive taxRate values unexplained.

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?

The description pairs the concrete verb 'Replace' with the specific resource 'editable contents of a quote or invoice draft', which clearly separates it from the create_quote_draft/create_invoice_draft siblings. It does not name or contrast an alternative sibling, so it stops short of 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 Guidelines2/5

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

The phrase 'using its current revision' hints at an optimistic-concurrency requirement, but there is no explicit statement of when to use this tool versus a draft-creation tool or an update_contract_draft sibling. An agent is left to infer both the trigger conditions and any preconditions.

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