Skip to main content
Glama

Outil.io

Update invoice

update_invoice
Destructive

Remplacer un brouillon, version requise. Les coordonnées de l’émetteur sont actualisées depuis les paramètres. Une facture émise est immuable.

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>",
      "data": "<data>"
    },
    "name": "update_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dataYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and 'Remplacer' is consistent with that. The description genuinely adds value by disclosing two behaviors not in the annotations: issuer contact details are silently refreshed from workspace settings, and issued invoices are immutable. It still does not say whether the supplied 'data' fully overwrites the draft or merges with it.

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?

Three very short sentences, no filler, with the core action stated first and the constraints following. Nothing is repeated and every clause carries 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 destructive replacement with a deeply nested payload it covers the key guardrails (draft-only, version required, issuer refresh), but leaves the replacement-vs-merge semantics and any post-call state undefined. With no output schema, the agent has no way to learn what the updated invoice looks like or what a version conflict returns.

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?

Schema description coverage is 0% and there are three required parameters including a large nested 'data' object. The description only illuminates 'version' (required for the replace/optimistic-lock semantics); 'id' and the whole 'data' structure (lines, client, dates, operation) get no added meaning whatsoever.

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 first sentence gives a specific verb and resource: replace a draft invoice, with a version required. Combined with the immutability note it separates this from create_invoice and issue_invoice, though it never names those siblings explicitly.

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?

It states a hard precondition ('brouillon' only) and a clear exclusion ('Une facture émise est immuable'), which tells the agent when this tool will fail. It stops short of naming the alternative to use for issued invoices, leaving that routing to inference from the sibling list.

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.