Skip to main content
Glama
tillbooks

tillbooks

Official

dashboard_series

Read-only

Generates monthly money-in and money-out series plus top expense accounts for finance dashboards, excluding internal bank transfers and opening postings.

Instructions

Die Diagramme der Übersicht: Geld rein und raus pro Monat und die grössten Aufwände (pure read, posts nothing). months[] holds every calendar month the range touches (clipped to it, at most 60), each with inMinor and outMinor in integer base-currency Rappen: the money in and out of the A19 Bankkonten's ledger accounts, netted per journal entry, so a transfer between two own bank accounts is neither in nor out, and the engine's own opening postings (Eröffnungsbilanz, Bank-Eröffnungssaldo) are left out because no money moved. totals sums them; Σ in − Σ out equals the bank accounts' net Kontoblatt movement over the window (general_ledger) minus those openings. topExpenses[] names the 5 (top, 1 to 12) largest Aufwand accounts of the range from income_statement (accountId, number, name, amountMinor), otherExpensesMinor is the rest of the expense accounts with a debit balance, grossExpenseMinor their sum (Σ top + other = gross), expenseReductionsMinor the expense accounts with a credit balance in the range (zero or negative: an Aufwandminderung or a stock change booked against material), and expenseTotalMinor the Erfolgsrechnung's net expense total (gross + reductions = total). bankAccounts counts the Bankkonten that fed the series (0 means no bank account yet: every month is 0, never an error). from > to answers invalid_range, a window over 60 months range_too_long, a workspace with no chart needs_chart.

Input Schema

NameRequiredDescriptionDefault
toYes
topNo
fromYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0-beta.2

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds substantial behavioral context: netting per journal entry, exclusion of transfers and opening postings, clipping to at most 60 months, zero-bank-account behavior, and specific error codes. These details go well beyond the annotation and are consistent with the read-only hint.

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?

The description is front-loaded with the core purpose and then unpacks the financial semantics, which is appropriate for a complex calculation. It is dense and contains long parenthetical sentences, but most details earn their place by explaining non-obvious behavior and edge cases.

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 no output schema and minimal annotations, the description carries the burden of explaining the return structure and covers months[], totals, topExpenses[], otherExpensesMinor, grossExpenseMinor, expenseReductionsMinor, expenseTotalMinor, bankAccounts, and relevant error conditions. It is complete enough for an agent to understand and call the tool correctly.

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 description must compensate for all four parameters. It explains that 'top' controls the number of largest expense accounts (1 to 12, defaulting to 5) and that 'from'/'to' define the range with validation and a 60-month cap, but it does not specify date formats or clarify workspaceId semantics.

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 clearly identifies the resource and content: monthly money-in/money-out charts and largest expense accounts for the dashboard. It is specific and distinguishes itself from general reports by focusing on dashboard series, but it does not explicitly name or contrast with sibling tools such as dashboard_overview or dashboard_tile.

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?

The description implies usage through 'Die Diagramme der Übersicht' and notes it is a pure read that posts nothing. It also documents error conditions (invalid_range, range_too_long, needs_chart), but it does not explicitly state when to use this tool versus dashboard_overview, dashboard_tile, or other reporting tools.

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

Deploy Server

Other Tools