Handelsregister

Search companies (AT + DE)

search_companies

Read-onlyIdempotent

Find companies across the Austrian Firmenbuch and the German Handelsregister - START HERE for any company lookup. Read-only.

    Parameters:
    - filters (optional): every field optional, AND-combined. Shared core (both
      countries): name (substring), query (MEANING-based hybrid search over the
      registered purpose - both countries), status (active|inactive|all, default all),
      legal_form, bundesland, city, postal_code (prefix; AT PLZ 4-digit, DE 5-digit),
      near {place | postal_code, radius_km} (radius search, matches from EVERY queried
      country within the radius - works across the border), nace_section (A-U; OENACE
      == WZ == NACE Rev. 2, so one industry code filters both countries), gegenstand
      (literal substring over the registered activity text), manager_name (person
      search), company_ids (prefixed watchlist, e.g. ["AT:123456a",
      "DE:D2601_HRB135076"], max 100). AT-only today (see describe_fields
      capabilities): nace_division/group, size_gkl, bilanzsumme/revenue/equity_ratio/
      employees ranges, growth_profile, has_guv(_latest), last_filing_year_min,
      founded_year_min/max, gf_age_min, event_signal/since/until. DE-only:
      registergericht, capital_min/max (Stammkapital). Country aliases
      (geschaeftszweig, oenace_*, wz_section, fnrs, stammkapital_*) are accepted.
    - sort (optional): {field, descending}. AT fields: bilanzsumme (default), revenue,
      equity_ratio, employees, last_filing_year, revenue_growth_1y/3y/5y, distance.
      DE fields: name, register_nummer, capital. A country that cannot sort by the
      requested field returns its default order (reported in notices).
    - page (default 1), page_size (default 25).
    - after (optional): KEYSET paging for bulk extraction - single country only
      (cursors are per register). Pass "" to start, then the country's next_after
      from per_country.
    - exact_count (optional, default false): force exact totals (costs a full scan).
    - country (optional, default "all"): "AT" | "DE" | "all".

    Returns {countries, total: {AT, DE, combined}, results, per_country, notices}.
    ``results`` are compact cards, each with ``country`` and the prefixed
    ``company_id``; with country="all" the list is AT block then DE block - each
    country keeps its own ranking (no fake interleave). ``per_country`` carries each
    register's own envelope (exact totals or lower bounds, applied_filters,
    relaxations on zero hits, query_mode, next_after). A filter one country does not
    support excludes that country and says so in ``notices`` - it is never silently
    dropped; an unreachable backend appears in ``countries_unavailable`` instead of
    failing the call. Never report a German company's financials as zero - DE
    financial data is not covered yet (see get_coverage).

    For one company's full profile use get_company_details; for a downloadable list
    use export_companies_csv; for dataset completeness use get_coverage.

Input Schema

TableJSON Schema

Name	Required	Default
`page`	No
`sort`	No
`after`	No
`country`	No	all
`filters`	No
`page_size`	No
`exact_count`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 20, 2026

addedInput schema / $defs / UnifiedSearchFilters / properties / nace_class

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Nace Class"
+}

addedInput schema / $defs / UnifiedSearchFilters / properties / oenace_class

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Oenace Class"
+}

addedInput schema / $defs / UnifiedSearchFilters / properties / wz_confidence_min

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Wz Confidence Min"
+}

First observedAug 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark it readOnly and idempotent. The description goes far beyond that by explaining key behaviors: unsupported filters exclude a country with a notice rather than being dropped, unreachable backends surface as countries_unavailable, DE financials are never reported as zero, and the result format includes per_country envelopes. It also reveals that results are not interleaved across countries. This is exemplary transparency beyond 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but every section earns its place given the tool's complexity. It is front-loaded with the core purpose and 'START HERE' directive, then organized by parameter groups earnestly. A minor deduction for verbosity—some stream-of-consciousness parentheses and inline asides could be tightened—but overall it is well-structured and information-dense.

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 tool with 7 parametersaving rich semantics, the description covers every aspect needed to call it correctly: full parameter list, default values, return structure, paging after, behavior on unsupported filters, and pointers to related tools. It even warns about a common pitfall (DE financials). Nothing critical 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?

Although the input schema itself lacks descriptions (0% coverage), the description thoroughly documents the semantics of filters, sort, paging, after, exact_count, and country. It explains AND-combination, cross-country near-radius behavior, country-specific fields, alias support, and sort fallback. This fully compensates for the schema gap.

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 a specific, action-oriented statement: 'Find companies across the Austrian Firmenbuch and the German Handelsregister - START HERE for any company lookup.' It names both the resource and the operation, and explicitly marks it as the entry point, setting it apart from sibling tools like get_company_details and export_companies_csv.

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 explicitly says 'START HERE for any company lookup' and then clearly delineates when to use alternatives: 'For one company's full profile use get_company_details; for a downloadable list use export_companies_csv; for dataset completeness use get_coverage.' This gives the agent unambiguous routing guidance.

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

All Handelsregister tools Inspect

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.