Skip to main content
Glama

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Official register document (DE)

get_document
Read-only

On-demand official register document for ONE German company. Read-only.

    Parameters:
    - company_id (required): "DE:{court}_{type}{number}" (e.g. "DE:D2601_HRB135076"); a bare
      German id works too. Austria is not supported here (its document flow is different).
    - kind (optional): "AD" = Aktueller Abdruck (current register extract, default) or
      "CD" = Chronologischer Abdruck -- the official Handelsregister abstract PDF; or
      "JA" = Jahresabschluss -- the company's newest official annual financial statement as
      published by the Unternehmensregister (served as the official HTML document, no PDF exists
      at the source).

    Returns a short-lived download link: {company_id, kind, url, bytes, cached, available,
    source, expires_at, expires_in_seconds} (plus year, stichtag for "JA"). AD/CD are fetched
    from handelsregister.de on demand (first call ~10 s, then cached); JA is served from the
    stored official publication. When the register holds nothing for that kind, ``available``
    is false with a ``note`` (never a dead link). A non-DE id returns an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoAD
company_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: ~10s cold latency then caching for AD/CD, JA served from the stored publication as HTML with no source PDF, the 'available=false + note' no-dead-link failure mode, short-lived link semantics, and an error on non-DE ids. These are exactly the traits annotations do not capture.

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?

Purpose is front-loaded in the first sentence, then tightly organized bullets for parameters and a compact run of return/behavior facts. Every sentence (Austria exclusion, latency, JA source format) carries information an agent needs.

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?

Despite an output schema existing, the description adds the non-derivable parts: id syntax, kind semantics, latency/caching, availability flag meaning, and error conditions. Nothing an agent needs to call it correctly is missing.

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?

With 0% schema description coverage, the description fully carries the burden: company_id's exact format with a worked example and the bare-id fallback, and all three 'kind' values (AD/CD/JA) with expansions and behavioral consequences including the default.

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+scope: 'On-demand official register document for ONE German company', with 'Read-only' clarifying the operation class. It is clearly distinguishable from siblings such as get_company_details or export_companies_csv without opening any schema.

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?

Gives concrete routing context: which 'kind' to pick and why, the limitation that Austria is not supported here, and that a non-DE id errors out. It never names a sibling as an alternative for the non-supported cases, so it stops short of explicit when-not/use-instead 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources