Skip to main content
Glama

Outil.io

Reverse accounting payment

reverse_accounting_payment

Annuler une saisie de règlement erronée avec une écriture inverse datée d’aujourd’hui. Pas de transfert 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>",
      "paymentId": "<paymentId>",
      "version": "<version>",
      "requestId": "<requestId>",
      "reason": "<reason>"
    },
    "name": "reverse_accounting_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonYes
versionYes
paymentIdYes
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.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses three useful behaviors: the correction is done via a compensating entry rather than a deletion, the reversing entry is dated today (not back-dated to the original), and no bank transfer occurs, so no money moves. The 'no bank transfer' note is consistent with destructiveHint=false and is exactly the kind of reassurance an agent needs before mutating accounting data. It does not mention what happens to the original entry's status or any permission requirements.

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?

Two short sentences, front-loaded with the action and the corrective mechanism; nothing is redundant. The terseness borders on under-specification, but no sentence wastes space.

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 five-required-parameter mutation with no output schema and only 20% schema coverage, so the description carries most of the burden and does not meet it. It never explains the identifier split, the version/concurrency requirement, the reason field's role, or the effect on the original entry. The French-only description alongside English tool and parameter naming adds a further comprehension burden for an English-oriented agent.

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?

Four of the five required parameters (id, paymentId, version, reason) carry no description in the schema, and the description adds nothing about them. In particular, the distinction between 'id' and 'paymentId' and the optimistic-concurrency meaning of 'version' are unexplained, which is a serious gap for a mutation tool where a wrong id is costly. Only requestId is documented, by the schema itself.

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 gives a specific verb-and-resource pair: cancelling ('annuler') an erroneous posted payment entry ('saisie de règlement erronée') by creating a reversing entry. This is more informative than the name alone because it explains the mechanism (contre-passation) rather than just 'reverse'. It does not name sibling tools such as reverse_accounting_expense or record_accounting_payment, so differentiation is left to the agent.

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?

Usage is implied by 'erronée' (use when a payment entry was recorded in error), which is a genuine trigger condition. However, there is no explicit when-not guidance (e.g., not for correcting a wrongly-recorded expense, which has its own sibling), and no alternative tool is named. The agent must infer the boundary from the adjective alone.

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.