Skip to main content
Glama

Outil.io

Get accounting journal

get_accounting_journal
Read-only

Journal de gestion en partie double et balance des comptes sur une période inclusive. EUR. Ventes, achats et règlements Outil seulement. Pas de clôture, déclaration TVA ou 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": "get_accounting_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 genuinely useful behavior context beyond that: the currency (EUR), the inclusive period semantics, and the covered transaction categories. It says nothing about output shape, volume or behavior when dates are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the purpose, so there is little waste. But it is telegraphic to the point of being fragmented ('Ventes, achats et règlements Outil seulement.'), which makes the exclusion clause harder to parse than necessary.

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 read-only, two-parameter tool with no output schema, the description should hint at what comes back (journal entries versus a balance table) and how the optional date bounds default. It conveys scope and currency adequately but leaves the agent guessing about the returned structure.

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 description coverage is 0% and neither 'from' nor 'to' is documented in the schema, so the description must compensate. It does partially by stating the period is inclusive, which resolves the key ambiguity about boundary handling. It does not say what happens when either bound is omitted (both are optional), nor which parameter is the start versus the end.

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 the resource and its content precisely: a double-entry management journal plus a trial balance over a period, limited to sales, purchases and settlements in EUR. An agent can distinguish this from a summary or document-retrieval tool. It does not name the sibling export tool it is not, so it falls short of a 5.

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?

Negative scope is stated ('Pas de clôture, déclaration TVA ou FEC'), which implicitly routes closing, VAT and FEC-export needs elsewhere. However, no alternative tool is named and there is no explicit positive 'use this when' statement, so the agent must infer the routing.

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.