Skip to main content
Glama

Handelsregister

by io.github.jkbngb

Register change feed (AT + DE)

list_events
Read-onlyIdempotent

Cross-company, cross-country feed of register CHANGES, newest first - the market-watch / deal-sourcing surface. Read-only.

    Parameters (all optional, AND-combined):
    - types: any of the SUPERSET enum - founding, new_registration, deletion,
      deletion_announced, name_change, seat_change, legal_form_change, capital_change,
      management_change, management_join, management_leave, gegenstand_change, merger,
      split, conversion, contribution, consolidation, division,
      shareholder_capital_change. Each country's feed carries a SUBSET; a type not in
      a country's feed is skipped for that country (reported in notices), and a
      country with none of the requested types is excluded. Note new_registration (DE,
      a discovery date) and founding (AT, a register event) are distinct - see
      describe_fields.
    - since / until: ISO dates. Default window: last 30 days.
    - bundesland: full state name.
    - nace_section (A-U, both countries); nace_division (AT only); legal_form (AT only).
    - company_ids: prefixed watchlist; AT filters the whole list, DE filters ONE id at
      a time (pass a single DE id, or query DE separately).
    - country: "AT" | "DE" | "all" (default). page (1), page_size (25).

    Returns {countries, events, per_country, windows, notices}. ``events`` are merged
    newest-first, each with ``country`` and a prefixed ``company_id``; AT events add
    before/after values only for the detailed types. ``windows`` states each country's
    data availability (AT: detailed >= 2026-07-01, coarse >= ~2020; DE: >= 2026-07-30)
    so an empty stretch is never mistaken for missing data. For aggregate counts use
    get_event_stats; for one company's history use get_company_details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sinceNo
typesNo
untilNo
countryNoall
page_sizeNo
bundeslandNo
legal_formNo
company_idsNo
nace_sectionNo
nace_divisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint, and the description substantially deepens behavioral context: it explains subset type skipping, per-country feeds, data availability windows so empty stretches are not misread, prefixed company_ids, and before/after values only for detailed AT types. No contradiction with annotations.

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?

The description is well-organized with a leading purpose sentence, a bulleted parameter list, and a compact return-value explanation. Every sentence or bullet adds essential operational detail without redundancy, making the length justified given the tool's API complexity.

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?

Given the output schema exists, the description still provides the important context that can't be inferred from schema: country-specific availability windows, AT/DE type distinctions, company_id constraints, and routing to sibling tools. It leaves the agent a fully operational understanding of when and how to invoke it.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully by documenting every parameter, including the full types superset enum, ISO date defaults, country-specific bounds for nace_division/legal_form, the company_ids AT/DE difference, and pagination defaults. It also states that all parameters are optional and AND-combined.

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 clearly states the tool lists cross-company, cross-country register changes, newest first, and labels it as the market-watch/deal-sourcing surface. This goes beyond the title by specifying scope, sorting, and data source, and it is immediately distinguishable from sibling tools that retrieve company details or aggregate stats.

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?

The description explicitly directs users to alternatives: 'For aggregate counts use get_event_stats; for one company's history use get_company_details.' It also explains parameter AND-combination semantics and country-specific type behavior, helping the agent decide when and how to call it.

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