Skip to main content
Glama

Handelsregister

by io.github.jkbngb

Register change statistics

get_event_stats
Read-onlyIdempotent

Aggregate counts of register changes by type and region, per country. Read-only.

    Parameters (all optional): since / until (default last 30 days); bundesland;
    nace_section; nace_division (AT); legal_form (AT); country ("AT" | "DE" | "all").

    Returns {countries, per_country, windows, notices}, each country's block being its
    own {total, by_type, by_bundesland}. Only AT exposes event statistics today; DE is
    reported in notices as not yet available (never as zero). For the individual
    changes use list_events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNo
untilNo
countryNoall
bundeslandNo
legal_formNo
nace_sectionNo
nace_divisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Read-only is already covered by annotations, but the description adds important non-obvious behavior: default date window, availability differences by country, the 'never as zero' rule for DE, and the top-level return shape. It exceeds annotation coverage without contradicting it.

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?

Four dense sentences, each adding value: the function's result, the parameter list, the availability caveat, and the sibling route. It is front-loaded with the primary purpose and avoids fluff.

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 7-parameter read-only tool with an output schema, this description covers parameter selection, default behavior, availability limitations and where to go for individual events. Nothing about selecting or invoking the tool correctly seems 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?

The input schema has zero parameter descriptions, but the description compensates by listing all parameters, marking them optional, giving the last-30-day default, restricting nace_division and legal_form to AT, and enumerating country values. It falls slightly short only because it does not spell out the expected string format for dates or explain the NACE/bundesland concepts.

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?

The description states a specific action and resource: aggregate counts of register changes by type and region per country. It also distinguishes itself from list_events, which is for individual changes, so an agent can select it correctly.

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?

It explicitly routes the agent to list_events for individual changes and makes the current availability clear: only AT exposes event statistics, while DE reports 'not yet available' instead of zero. This gives both positive and negative usage guidance.

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

All Handelsregister toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation4/5

Each tool has a distinct primary purpose, with clear pointers to the right tool for the job. The main possible confusion is between describe_fields/get_coverage and search_companies/search_person, but the descriptions actively disambiguate those boundaries.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern: describe_fields, export_companies_csv, get_company_details, list_events, search_companies. Even ping fits the predictable style as a simple liveness verb.

Tool Count5/5

Eleven tools is well-scoped for a unified company-register facade. Each tool covers a distinct part of the surface: schema, coverage, search, detail, persons, peers, events, statistics, export, and diagnostics.

Completeness5/5

The read-only domain is covered thoroughly: lookup, detail, person search, similarity, event feeds, aggregate stats, and export all exist. Unsupported country-specific features are handled with notices and coverage metadata rather than missing tooling.

Resources