Skip to main content
Glama

Outil.io

Create invoice credit

create_invoice_credit

Émettre un avoir INTÉGRAL avec motif, figer son PDF et inverser la vente. Annule la facture et indique le montant déjà encaissé à rembourser. Ne déclenche aucun remboursement bancaire.

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>",
      "requestId": "<requestId>",
      "reason": "<reason>"
    },
    "name": "create_invoice_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonYes
versionYes
requestIdYesUUID stable pour les reprises de la même opération ; nouvel UUID si les données changent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the concrete effects: the credit note is integral, its PDF is frozen, the sale is reversed, the invoice is cancelled, and the amount already collected is surfaced. It also rules out a bank refund, which is the single most important behavioral caveat for an agent. There is a mild tension with destructiveHint=false ("annule la facture", "inverser la vente"), but the description reconciles it by clarifying that no money movement occurs — the invoice is compensated, not erased.

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?

Three dense sentences, front-loaded with the action and scope, then effects, then the critical caveat about no bank refund. Nothing is padding. Minor cost: "inverser la vente" is business jargon that adds ambiguity rather than precision.

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 mutation tool with no output schema, the effect side is well covered (cancellation, PDF freeze, refund exposure). What is missing is what the call returns (a credit note id?), whether the credit itself can be reversed, and the version/conflict semantics — all things an agent needs before firing a one-way accounting operation.

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 coverage is only 25%: requestId is the sole documented parameter. The description's "avec motif" at least confirms reason is mandatory, but it says nothing about the id+version pair, which is clearly an optimistic-concurrency contract the agent must understand (pass the current version, expect a conflict otherwise). At this coverage level the description should compensate and does not.

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?

"Émettre un avoir INTÉGRAL" names a specific verb (issue) and resource (credit note) and pins the scope with the emphatic INTÉGRAL, which implicitly excludes partial credits. It also states the downstream effect ("Annule la facture"). It never names a sibling such as create_invoice or update_invoice, so the agent must infer routing from the "full credit only" framing.

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 word INTÉGRAL implies this is the wrong tool for a partial credit, and "Annule la facture" signals the trigger condition (a sale that must be fully reversed). But no alternative is named for partial credits, corrections, or draft deletion, and no prerequisites are stated, so usage 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.