Skip to main content
Glama

Outil.io

Update quote

update_quote
Destructive

Modifier un devis BROUILLON (version requise, lire get_quote). Un devis envoyé est figé : en créer un nouveau.

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>",
      "version": "<version>"
    },
    "name": "update_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNoObjet du devis
linesNo
notesNo
termsNo
clientNoCoordonnées imprimées (reprises du contact si absent)
dealIdNoOpportunité CRM passée à won à l’acceptation
versionYes
currencyNo
discountNoRemise globale HT
durationNo
contactIdNo
startDateNo
vatExemptNoMicro-entreprise : TVA non applicable, art. 293 B du CGI
prospectIdNo
validUntilNo
paymentTermsNo
validityDaysNoAlternative à validUntil (30 jours par défaut)
depositPercentNoAcompte demandé à l’acceptation
requireSignatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real value on top: the draft-only restriction, the requirement to fetch the current version first, and the frozen-state rule. It does not disclose the semantics that matter most for a destructive update with 20 parameters, such as whether omitting a field clears it or whether the nested lines array replaces all existing lines.

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 sentences, front-loaded, with no filler: the scope constraint comes first, then the prerequisite, then the forbidden case and its remedy. Every clause carries operational information.

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

Completeness3/5

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

For a 20-parameter nested mutation with no output schema, the definition covers the critical gotchas (draft-only, version concurrency, send-after-freeze alternative) but leaves open what a version conflict looks like, whether this is a full or partial update, and what the destructive hint implies for existing lines and client data.

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 only 35%, so the description carries more of the burden than usual, and it does explain why version is required (read it via get_quote) and what happens to the state (frozen once sent). It says nothing about the other 18 parameters, including the high-impact fields lines, client, discount, and validityDays, so the remaining coverage gap is not compensated.

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?

The description gives a specific verb (Modifier) with a precisely scoped resource (un devis BROUILLON), so an agent can immediately tell it apart from create_quote and from the read path get_quote.

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

Usage Guidelines5/5

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

It states the condition for use (draft only), the exclusion (a sent quote is frozen), the alternative action (create a new one), and the prerequisite read (lire get_quote for the version). Nothing about when to use it is left to inference.

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.