agentic-firmenbuch

Overview Schema Source Related Servers Discussions Admin

Register change statistics

get_event_stats

Read-onlyIdempotent

Aggregate Austrian company register changes by type and Bundesland over a date window for market-watch dashboards, e.g. capital increases in OÖ this month.

Instructions

Aggregate counts of register changes by type and by Bundesland over a window. Read-only. Pro. Use for market-watch dashboards ("how many capital increases in OÖ this month"); for the individual changes use list_events.

    Parameters (all optional): since / until (default last 30 days); bundesland; oenace_section;
    oenace_division; legal_form — same facets as list_events. Returns {since, until, total,
    by_type, by_bundesland}. Forward-only from 2026-07-01.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	No
`until`	No
`bundesland`	No
`legal_form`	No
`oenace_section`	No
`oenace_division`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, so safety is handled. The description adds useful traits beyond structured data: the 30-day default window and the 'Forward-only from 2026-07-01' coverage constraint, which materially affects whether results are trustworthy for older periods. Minor gap in not explaining aggregation semantics or pagination, but the coverage boundary is the important disclosure.

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?

Front-loaded with the core purpose in the first sentence, then usage, then parameters and return shape. Every block earns its place, though the fragmentary 'Read-only. Pro.' and mixed paragraph/list formatting read slightly unpolished.

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 six-parameter, all-optional aggregation tool with an output schema, the description supplies purpose, alternative routing, parameter defaults, and the coverage window. Nothing essential to calling it correctly is missing.

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?

Schema description coverage is 0%, so the description must compensate, and it mostly does: it labels all six parameters, marks them optional, gives the since/until default, and notes the facet parameters match list_events. It stops short of giving accepted formats or example values for since/until or coded values for oenace/legal_form.

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 specific verb+resource ('Aggregate counts of register changes by type and by Bundesland over a window') and explicitly distinguishes itself from the sibling list_events, which handles individual changes. An agent can select between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('market-watch dashboards') with a concrete example and names the alternative tool plus the condition that selects it ('for the individual changes use list_events'). This is textbook when/when-not guidance.

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

Deploy Server