Skip to main content
Glama

Outil.io

Update contract

update_contract
Destructive

Modifier un contrat BROUILLON (version requise).

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_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
htmlNoContrat HTML libre (h1-h3, p, ul/li, strong, table) avec {{variables}}
nameNo
dealIdNo
signerNo
quoteIdNoDevis lié : prix, objet et client repris
versionYes
contactIdNo
variablesNoValeurs : object, price, duration, startDate, deliverables, paymentTerms, client.{name,company,address,siret}…
templateIdNoModèle personnalisé (ressource contract_templates)
templateKeyNoModèle intégré (prestation-services par défaut) : list_contract_templates

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?

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false; the description adds genuinely useful behavioral context by restricting the operation to DRAFT contracts. However, it does not say whether omitted fields are preserved or nulled, whether a stale version fails the call, or what happens on success, which matters a lot for a destructive 11-param mutation.

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 short sentence with no filler, and the key constraint is front-loaded. Its terseness is arguably under-specification rather than poor structure, but nothing is wasted.

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?

For a destructive, nested-object, 11-parameter update with no output schema and 45% schema coverage, one sentence covering only draft status and version is far too thin. The agent cannot tell how partial updates behave or how the quote/template/variable parameters interact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 11 parameters and only 45% schema description coverage, the description must carry meaning but instead only mentions version. It says nothing about id, dealId, quoteId, contactId, signer, variable substitution, or the templateId/templateKey distinction, leaving several undocumented parameters uninterpretable.

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 ("Modifier un contrat") plus a scoping constraint ("BROUILLON") that clearly separates it from create_contract and delete_contract by lifecycle state. It omits any explicit sibling routing, 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 Guidelines3/5

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

The parenthetical "(version requise)" implies the caller must supply the current version, and "BROUILLON" implies only draft contracts are eligible. No when-not guidance or alternatives (e.g. cancel_contract, create_contract) are named, so the usage guidance is only implied.

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.