Skip to main content
Glama

Administratie exporteren

export_books
Read-only

Export a full year of bookkeeping data as JSON—business profile, invoices, expenses, filed btw returns, year report, and tax rules—for bookkeeper handoff, backup, or leaving Bookiz.

Instructions

Everything for one year as JSON: business profile, invoices, expenses with receipt hashes, filed btw returns, the year report and the tax rules used. For a bookkeeper, a backup, or leaving Bookiz.

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": {
      "year": "<year>"
    },
    "name": "export_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 exactly what data is bundled (including receipt hashes and the tax rules used), which is what an agent needs to judge whether a full export is warranted. It stops short of noting volume or time cost of a full-year export.

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?

Two sentences, zero filler. The content enumeration is front-loaded before the use cases, so the agent reads scope before motivation.

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?

With no output schema, the description carries the burden of describing the return value and does so by listing the bundled data as JSON. For a read-only export with one parameter, this is nearly complete; only the year format and any size/timing caveats are missing.

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%, so the single 'year' parameter is documented nowhere structurally. The phrase 'for one year' conveys that the parameter scopes the export to a year, but it does not clarify the format (e.g. 2024 vs '2024') or whether it is calendar or fiscal year, which is a real gap for a tax-related export.

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 states a concrete resource and enumerates its contents precisely: business profile, invoices, expenses with receipt hashes, filed btw returns, year report and tax rules. That enumeration distinguishes it from siblings like year_report or list_invoices without needing to name them. The verb is only implicit ('Everything ... as JSON'), but the scope is unmistakable.

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?

Three intended scenarios are given ('for a bookkeeper, a backup, or leaving Bookiz'), which tells the agent when this tool is appropriate. However, it offers no exclusions and no routing to alternatives, e.g. that year_report alone suffices if only the report is wanted rather than a full backup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.