Skip to main content
Glama

Outil.io

Reverse accounting expense

reverse_accounting_expense

Extourner une dépense non réglée avec motif. La pièce et les écritures d’origine sont conservées. Annuler ses règlements avant cette action.

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": "reverse_accounting_expense"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false and readOnlyHint=false, so the description adds real value by explaining that the original document and accounting entries are preserved rather than deleted, which explains why the flag is false. It also states a reason is mandatory. It stops short of describing what the response returns or whether the reversal is itself reversible.

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 short sentences, each carrying distinct information: what the operation does, what is preserved, and the precondition. The key scoping constraint ('non réglée') is front-loaded.

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 and 25% parameter coverage, the description covers the safety profile and precondition adequately but leaves the concurrency contract (version) unexplained and says nothing about failure modes when the expense is already settled or the version is stale.

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 only 25% (only requestId is documented), so the description must compensate. It only implies the 'reason' parameter via 'avec motif'; the critical 'version' parameter (an optimistic-concurrency token, exclusiveMinimum 0) and 'id' are given no meaning in either place, leaving the agent to guess how to satisfy the version requirement.

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 states a specific verb ('Extourner') and resource ('une dépense'), and narrows the scope with the qualifier 'non réglée' (unpaid), which distinguishes it from a generic expense update. It does not name the sibling reverse_accounting_payment, but the operation is clearly identifiable from the text alone.

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 gives an explicit precondition: 'Annuler ses règlements avant cette action' tells the agent to remove payments first, effectively routing it toward the payment-reversal tool when payments exist. What is missing is a positive statement of when reversal is preferable to editing or deleting the expense.

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.