Fibalo

Reports: BWA

bwa_report

Read-onlyIdempotent

DATEV-BWA (Betriebswirtschaftliche Auswertung, Kurzfristige Erfolgsrechnung) for a month or a period.

The monthly management report a Steuerberater hands out, in the DATEV row layout: revenue, cost blocks and the result for the period and cumulated from the start of the business year, with each row's share of Gesamtleistung and Gesamtkosten. The period must lie inside one business year. Needs full access to the company. Figures follow the Kontierung in Fibalo, so a month with unreviewed Belege is incomplete: say so when you quote it.

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": {
      "company": "<company>",
      "from_month": "<from_month>",
      "to_month": "<to_month>"
    },
    "name": "bwa_report"
  }
}

Input Schema

Name	Required	Description	Default
`as_pdf`	No	true returns a download link to the report as a PDF (`url`, valid 15 minutes) instead of the figures. Give the user the link as it is.
`company`	Yes	company name or id.
`to_month`	Yes	YYYY-MM, last month of the report, not before from_month, same business year.
`from_month`	Yes	YYYY-MM, first month of the report.
`kontierung`	No	bestaetigt counts only confirmed account assignments (default), vorschlag also counts Fibalo's suggestions that nobody confirmed yet.	bestaetigt
`mit_konten`	No	true adds the Kontennachweis, the accounts behind every row.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent safety, and the description adds real context beyond them: the full-access requirement, the single-business-year restriction on the period, and the crucial data-freshness caveat that figures follow the Kontierung in Fibalo so a month with unreviewed Belege is incomplete. That caveat materially changes how an agent should present results.

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 sentences, front-loaded with the artifact and its scope, then content, then constraints and the caveat. No filler. Slightly dense with German domain terms, but every clause carries information.

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

Completeness5/5

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

With an output schema present and 100% schema coverage, the description only needs to supply intent, constraints and caveats — which it does, including the auth requirement and the incompleteness warning. An agent can call this correctly and report it honestly.

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 100%, so the schema already documents as_pdf, kontierung, mit_konten and the month formats. The description only reinforces the business-year constraint on to_month and does not add syntax or meaning for as_pdf, kontierung or mit_konten beyond what the schema states. Baseline 3 is appropriate.

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?

Names a specific artifact ('DATEV-BWA ... Kurzfristige Erfolgsrechnung') and states its scope ('for a month or a period'), plus what the report contains (revenue, cost blocks, result, cumulative from start of business year, share of Gesamtleistung/Gesamtkosten). This clearly separates it from ustva_report, susa_report and bwa_jahresuebersicht by scope, though no sibling is named explicitly.

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?

'Needs full access to the company' gives a precondition, and 'The period must lie inside one business year' gives a hard constraint on when the call is valid. It also tells the agent to caveat a month with unreviewed Belege when quoting figures. What is missing is an explicit 'use bwa_jahresuebersicht instead when you need a full year' routing statement.

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

All Fibalo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?