Skip to main content
Glama

check_german_company_kyb

Run a German KYB audit by checking Handelsregister records and insolvency announcements to verify company identity, register details, and financial information.

Instructions

Run a German KYB audit against official Handelsregister (XJustiz) and Insolvenzbekanntmachungen.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cityNoRegistered city / seat to narrow Handelsregister results, e.g. 'Mainz'.
companiesNoBatch list of companies (names, 'Name | City | HRB' strings, or dicts).
company_nameNoFull or partial legal name of a German company, e.g. 'BioNTech SE'.
register_typeNoOfficial German register type filter.ALL
register_numberNoCommercial register number with or without prefix, e.g. 'HRB 48720'.
request_delay_secondsNoPolite delay in seconds between sequential batch checks (0-10).
include_insolvency_checkNoCross-check against official insolvenzbekanntmachungen.de announcements.
include_financial_detailsNoParse XJustiz/SI XML filings for share capital, officers, and corporate purpose.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It names the official registers queried, which adds some source context, but it does not disclose read-only versus write behavior, external request implications, batch semantics, rate limiting, or what the insolvency and financial detail options change.

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 a single front-loaded sentence with no filler. It states the action and data sources immediately, though it is terse for an eight-parameter auditing tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with eight parameters, batch processing, optional insolvency and financial-detail checks, and no annotations. The output schema covers return values, but the description remains too thin on behavior, usage conditions, and operational caveats to fully orient an agent.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters such as city, companies, register_type, and request_delay_seconds are already well documented. The description adds no parameter-specific meaning beyond naming the underlying data sources.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Run a German KYB audit,' and names the official data sources Handelsregister (XJustiz) and Insolvenzbekanntmachungen. It is clear what the tool does, but it does not explicitly differentiate this from the German-related sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, nor does it state prerequisites, exclusions, or recommended scenarios. Usage is only implied by the tool name and the term 'KYB audit.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.