Skip to main content
Glama
tillbooks

tillbooks

Official

dashboard_overview

Read-only

Generates a live KPI tile wall for a date range, showing revenue, cash, AR/AP aging, utilisation, margin, VAT due, stock value and bank inbox figures from existing read models.

Instructions

Die Übersicht (dashboard): one KPI tile wall for a date range, composed live from the read models the product already computes and never cached (pure read, F00 posts nothing and owns no tables). Core tiles: revenue | cash | ar_aging | ap_aging | utilisation | project_margin | mwst_due | stock_value | bank_inbox, each an integer-Rappen (or basis-point) figure that equals its source verb's answer for the same filter: revenue from income_statement (the Nettoerlöse section, with a previous-window trendBp), cash from the A19 bank accounts' Kontoblatt closing balances (general_ledger), AR from aging_report, AP from list_vendor_bills, utilisation as the billable share of time_list minutes (B01 has no capacity model), margin from costing_pl_list, MWST due verbatim from vat_return for the settlement period containing the range end, stock value from stock_valuation_report under the books' method. bank_inbox is the Bankeingang band (current, not ranged): the open bank lines, those that need you, the sure proposals and the lines booked to accounts without a Beleg, each by list_bank_inbox's own per-line definitions, per Bankkonto with money in and out, plus the last statement fetch, a fetch running now, the daily automatic fetch (autoMode, nextAutoSyncAt, lastAutoOutcome) and autoAvailable (false when this process runs no scheduler, e.g. till serve). Every tile embeds a drill descriptor (studioRoute, mcpTool, params) naming the EXISTING source tool behind the number: call that tool for the rows. Tiles the caller's A24 role may not see are omitted server-side into omitted[] (per-tile gates: read_books, read_sales, read_vat, read_master_data, time.read, costing.read); an unconfigured or unused module degrades its one tile to ok:false with the source's own code (needs_vat_config, needs_chart, needs_projects, needs_stock_items) while the rest still render; an empty workspace answers ok:true zero states, never an error. from > to answers invalid_range. savedViewId applies a G00 saved view (entityKind 'workspace', layout 'dashboard') to restrict and order tiles; an unresolvable view falls back to the full default with viewFallback:true and can never widen access.

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
savedViewIdNo
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds a great deal beyond that: never cached, F00 posts nothing and owns no tables, per-tile role gating into omitted[], module degradation to ok:false with source codes, empty workspace answering ok:true zeros, invalid_range for from>to, and saved-view fallback that can never widen access.

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 purpose is front-loaded, but the body is a single dense run-on paragraph of roughly 350 words packed with parentheticals and German domain jargon. Much of it earns its place, yet the exhaustive per-tile source-verb mapping and scheduler internals (autoMode, nextAutoSyncAt, lastAutoOutcome) exceed what is needed to invoke the tool.

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?

For a complex multi-tile aggregate with no output schema, the description still covers the response shape (tiles with ok flags, omitted[], viewFallback, drill descriptors), the degradation and permission paths, and the error cases. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry the burden, and it does for three of four params: from/to define the range (with the from>to error case) and savedViewId is explained in detail (G00 view, entityKind 'workspace', layout 'dashboard', fallback semantics). workspaceId is only implied, never described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource: a single KPI tile wall for a date range, composed live from read models. It enumerates the concrete tiles (revenue, cash, ar_aging, ...) and their exact source verbs, so an agent knows this is an aggregate overview, not a row-level report.

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?

Clearly routes the agent away from this tool for detail: 'Every tile embeds a drill descriptor ... call that tool for the rows', and savedViewId is described as restricting/ordering tiles. It never explicitly contrasts with the closest siblings (dashboard_tile, dashboard_series, attention_summary), so the alternative-selection guidance is present but incomplete.

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