Skip to main content
Glama

Handelsregister

by io.github.jkbngb

Liveness / server info

ping
Read-onlyIdempotent

Liveness probe: confirms the unified register server is up. Read-only.

    Parameters:
    - check_backends (optional, default false): when true, additionally performs a
      cheap connection handshake against every configured country backend and reports
      per-country reachability ("ok" / "unreachable").

    Returns {status, server, countries, provenance} - countries maps each configured
    country code to its backend product name and, with check_backends, its live
    reachability. Use get_coverage for data completeness; this tool only says whether
    the service is up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
check_backendsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds transparency beyond annotations by explaining the optional 'cheap connection handshake' against every configured backend and how per-country reachability is reported, plus the high-level response shape.

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?

The description is structured and info-dense: a one-line purpose, a parameter breakdown, and a return summary. It loses a point for a little redundancy: 'confirms the server is up' and 'only says whether the server is up' say similar things.

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 simple liveness tool with one optional parameter, an output schema, and strong annotations, the description fully covers what the agent needs: purpose, parameter semantics, return contents, and how it differs from the relevant sibling. Nothing essential 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?

The schema has 0% description coverage, so the description carries the full parameter documentation burden. It fully explains check_backends: its default(false), optional nature, behavior when true, and the per-country reachability information it produces.

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 opens with 'Liveness probe' and says it 'confirms the unified register server is up,' giving a specific verb and resource. It also explicitly distinguishes itself from get_coverage by stating 'this tool only says whether the server is up,' which prevents confusion with a sibling.

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 names the alternative get_opcoverage for data completeness and clearly states the boundary of this tool. The optional check_backends parameter is also described with its effect, telling the agent when it is appropriate to invoke the deeper behavior.

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