Skip to main content
Glama

Outil.io

Get accounting document

get_accounting_document
Read-only

Lire une pièce et sa version avant modification ; inclut lignes, mentions figées, historique des règlements et solde.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond them by disclosing the payload contents (lines, frozen mentions, payment history, balance) and the read-before-modify expectation, compensating for the absent output schema. No auth or error behavior is described.

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?

One dense sentence with the read action and its rationale ('avant modification') front-loaded, followed by the returned content. Nothing is wasted and no filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-parameter fetch with no output schema, the description supplies the key missing piece: what the response contains. It is nearly complete; only error behavior and identifier semantics are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'id' parameter is documented nowhere beyond its uuid format. The description says nothing about the identifier, though for a one-parameter lookup keyed by id the meaning is largely self-evident from the name and format, so the gap is mild.

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 (Lire) and resource (pièce / accounting document), and enumerates what the read includes: lines, frozen mentions, payment history and balance. It is clearly a document-fetch tool, distinguishable from list/replace/write siblings, though it never names an alternative explicitly.

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?

'avant modification' implies the intended moment of use (fetch current state/version prior to an edit), which is useful context. However there is no guidance on when not to use it, no mention of the list tool for discovery, and the 'version' aspect (concurrency token) is only hinted at.

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.