Skip to main content
Glama

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Official register document (DE)

get_document
Read-only

On-demand official register PDF 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),
      "CD" = Chronologischer Abdruck.

    Fetches the official PDF from handelsregister.de on demand (first call ~10 s, then cached)
    and returns a short-lived download link: {company_id, kind, url, bytes, cached, available,
    source, expires_at, expires_in_seconds}. 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?

Annotations already indicate readOnly and non-destructive, but the description adds valuable behavior: on-demand fetch from handelsregister.de, caching (first call ~10s), short-lived download link, response fields, the 'available: false with note' failure mode, and non-DE error behavior. This far exceeds the structured 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 information-dense but every sentence adds value: purpose first, then parameter definitions, then behavior and output shape. The structured parameter listing and response field enumeration are efficient and easy to parse.

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 tool's complexity, the description is complete: input format, supported/unsupported regions, optional parameter defaults, caching, response fields, failure semantics, and error cases are all covered. Nothing essential is missing for correct invocation.

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%, so the description carries the full burden. It thoroughly explains company_id format with a concrete example and the tolerated bare German id, and it defines both kind values ('AD' and 'CD') with their meanings and default. This compensates completely for the empty schema.

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 verb ('Fetches the official PDF'), a precise resource ('official register PDF for ONE German company'), and a clear scope ('ONE German company', 'Austria is not supported'). This distinguishes it from sibling tools focused on search or company details without ambiguity.

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?

The description clearly indicates when the tool is appropriate (one German company, known company_id, on-demand PDF) and when it is not (Austria, non-DE IDs return an error). It does not explicitly name sibling alternatives, but the scope restriction and error behavior effectively guide selection.

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