Skip to main content
Glama
Sign In

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Search a person across registers

search_person
Read-onlyIdempotent

Beispiel: „Welche Firmen führt eine Person namens Maria Huber?“

Find every company a person runs or represents - across BOTH registers in one call (cross-border person search). Read-only.

    Parameters:
    - name (required): person name substring, case-insensitive, e.g. "Mustermann".
    - country (optional, default "all"): "AT" | "DE" | "all".
    - page_size (optional, default 25): results per country.
    - status (optional, default "all"): "active" | "inactive" | "all".

    Returns the merged search_companies envelope ({countries, results, per_country,
    notices}) plus ``person_query``; every result card carries ``country``,
    ``company_id`` and the matched manager. AT matches the primary managing director,
    DE matches all managing directors AND registered signatories. IMPORTANT: matching
    is by name and the registers publish birth YEAR only - a shared name across
    companies or countries does not prove the same person (the notice says so; use
    birth years and context to corroborate). For general company search use
    search_companies with other filters; manager_name can be combined there too.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "search_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
statusNoall
countryNoall
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare read-only/idempotent, but the description adds register-specific matching semantics (AT matches the primary managing director, DE matches all managing directors AND signatories) and a critical data-quality caveat that name matches across companies or countries do not prove identity because only birth year is published. That is exactly the kind of context structured fields cannot carry.

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?

Front-loaded with the example query, then parameters, then return/behavior notes - a sensible order with no filler sentences. It is on the long side and repeats the return envelope that the output schema already defines, costing a point.

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 four-parameter search tool with sparse schema documentation, the description covers inputs, per-country matching behavior, return shape, and the identity-resolution caveat. An agent can call it correctly and interpret results without further inference.

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 must compensate, and it does: it documents all four parameters with required/optional status, defaults, allowed values ('AT' | 'DE' | 'all', 'active' | 'inactive' | 'all'), and semantics (case-insensitive name substring, page_size per country). The enum values are absent from the schema and supplied only here.

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 and resource ('find every company a person runs or represents') plus a scope qualifier ('across BOTH registers in one call'). It distinguishes itself from the sibling search_companies by name and explicitly routes general company queries there.

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?

Opens with a concrete example question, states the use case (cross-border person search), and explicitly names the alternative: 'For general company search use search_companies with other filters; manager_name can be combined there too.' When-to-use and when-to-use-something-else are both covered.

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