Skip to main content
Glama

Outil.io

Record accounting payment

record_accounting_payment

Constater un règlement réellement effectué, en CENTIMES EUR. Facture : encaissement ; dépense : décaissement ; avoir : remboursement. Interdit le dépassement du solde. Ne déplace pas d’argent.

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>",
      "requestId": "<requestId>",
      "version": "<version>",
      "amount": "<amount>",
      "date": "<date>",
      "method": "<method>",
      "reference": "<reference>"
    },
    "name": "record_accounting_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dateYes
amountYes
methodYes
versionYes
referenceYes
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?

Annotations only declare the write/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds genuinely new behavior: amounts are in euro cents, overdrawing the outstanding balance is rejected, and no funds are actually moved. It does not mention idempotency or retry behavior, which the requestId schema hints at but the description never reinforces.

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?

Four short clauses, front-loaded with the action and the unit convention, with no filler. The telegraphic French fragments are dense but still parseable; a slightly more explicit sentence structure would cost nothing.

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 with 7 required parameters, no output schema, and near-zero schema documentation, the description covers the critical business rule (no overdraft) and units but leaves versioning, reference, and method semantics unexplained. An agent could invoke it correctly only by guessing at several required fields.

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 14% (only requestId is documented), so the description carries most of the burden and delivers only the unit convention for 'amount' (CENTIMES EUR). Six required parameters — id, version, date, method, reference, and the balance-checking semantics of amount — get no explanation of format, locking behavior, or allowed values.

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 ('constater un règlement réellement effectué') and clarifies the direction for each document type (facture = encaissement, dépense = décaissement, avoir = remboursement), which meaningfully separates it from record_accounting_expense. It stops short of naming the sibling tools it complements or replaces, so an agent must still infer the routing.

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 phrase 'réellement effectué' implies this is only for payments that have actually occurred, and the balance rule implies a precondition, but neither is framed as an explicit when-to-use/when-not-to-use rule. No alternative is named for corrections (e.g. reverse_accounting_payment) or for recording a planned versus settled payment.

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.