Skip to main content
Glama

Outil.io

Export accounting journal

export_accounting_journal
Read-only

Exporter le journal en CSV de travail, protégé contre les formules de tableur. Renvoie filename et text. Ce fichier n’est pas un FEC.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the CSV is protected against spreadsheet formula injection, and it returns 'filename' and 'text' — both facts an agent cannot get from the annotations or schema. It stops short of noting whether the export is limited in row count or how the journal is ordered.

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, front-loaded with purpose, then return shape, then the FEC caveat. Nothing is redundant and each sentence carries distinct information.

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?

It usefully discloses the return values in lieu of an output schema and flags the FEC distinction. But for a tool whose only inputs are two undocumented date parameters, omitting any statement about what period is exported leaves the caller unable to predict the result set.

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%: the two parameters 'from' and 'to' have only a date pattern and no description of what they filter. The description never mentions date bounds at all, so the agent must guess that these bound the journal period rather than, say, a creation or posting date. This is the clearest gap in the definition.

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 and resource ('Exporter le journal') plus the output format ('CSV de travail'), and adds a differentiating scope note ('Ce fichier n'est pas un FEC') that separates it from a statutory FEC export. It is clear what the tool produces, though the all-French phrasing sits oddly against English tool names and sibling names, which slows matching slightly.

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?

There is an implicit when-not ('Ce fichier n'est pas un FEC') that steers the agent away from this tool for statutory filing, which is useful. However, there is no explicit guidance on when to choose this over get_accounting_journal or the other export_* siblings, and no mention of the date-range scope that the schema implies.

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.