Skip to main content
Glama

Outil.io

List accounting documents

list_accounting_documents
Read-only

Lister factures Outil, avoirs et dépenses : montants en centimes EUR, solde et version. 50 par page. Les factures Stripe restent dans list_records invoices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_accounting_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
pageNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: amounts are returned in euro cents, records include balance and version, and results are paginated at 50 per page. It does not explain ordering or sorting of the returned pages, which is a small remaining gap.

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 short clauses, front-loaded with the core listing scope and followed by the units/pagination facts and then the alternative routing. Nothing is redundant. Slight density loss from terse French abbreviations embedded next to English tool names, but no wasted sentences.

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 four-parameter read-only list tool with annotations covering the safety profile and no output schema, the description supplies return-value facts (cents, balance, version, page size) that an agent needs. However, it leaves every filter parameter undefined, so an agent cannot confidently construct a filtered query from the definition alone.

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 0%, so all four parameters (q, kind, status, page) rely entirely on the description, yet none of them is mentioned—no note on what q searches, what the enum values mean, or whether page is 1-based. The only indirect hint is '50 par page', which implies page has an effect but gives no starting index. With enums on two parameters, the omission of value semantics is a real cost.

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 names a specific verb ('Lister') plus the resources covered ('factures Outil, avoirs et dépenses'), and explicitly carves out Stripe invoices. This lets an agent distinguish it from list_records. Minor friction: the text mentions credit notes ('avoirs') while the schema's kind enum only offers invoice|expense, so the stated scope is slightly broader than what the tool actually filters.

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?

The final sentence gives an explicit routing rule: Stripe invoices stay in list_records (invoices). That is a clear when-not-to-use statement naming the alternative. No guidance is offered for choosing among get_accounting_document, export_accounting_journal, or get_accounting_summary, but the principal confusion is resolved.

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.