Skip to main content
Glama

Firmenbuch

by io.github.jkbngb
OverviewDiscussionsAdmin

Company profile (AT + DE)

get_company_details
Read-onlyIdempotent

Beispiel: „Wer führt die Red Bull GmbH und wie hoch ist die Eigenkapitalquote?“

Full profile for ONE company, routed by its unified id. Read-only.

    Parameters:
    - company_id (required): "AT:{fnr}" (e.g. "AT:123456a") or
      "DE:{court}_{type}{number}" (e.g. "DE:D2601_HRB135076"); bare national ids are
      accepted too. Take it from a search card's ``company_id``.
    - max_signatories (optional, DE only): cap on the served officer list (DE default
      15, 0 = all); ignored for AT.

    Returns the country backend's full profile plus ``country`` and the prefixed
    ``company_id``. AT: identity, location, per-year Bilanz + GuV, ratios, growth,
    filings, management, events. DE: identity, seat, Stammkapital, Gegenstand, WZ/NACE
    classification, managing directors (birth year only), and the parsed
    Jahresabschluss (Bilanz, ratios, GuV where published) for companies the rollout
    has reached - ``financials.reporting_status`` says whether figures exist, the
    source publishes none, or the company has not been processed yet, so never report
    missing German figures as zero. Unknown id ->
    {error: not_found}. Use search_companies first when you only have a name.

Input Schema

NameRequiredDescriptionDefault
company_idYes
max_signatoriesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / company_id
      Added value: +{
+  "title": "Company Id",
+  "type": "string"
+}
    • removedInput schema / properties / fnr
      Removed value: -{
-  "title": "Fnr",
-  "type": "string"
-}
    • addedInput schema / properties / max_signatories
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Signatories"
+}
    • changedInput schema / required
      Previous value: -[
-  "fnr"
-]New value: +[
+  "company_id"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint/idempotent, which the description echoes as 'Read-only'): it declares the unknown-id outcome ({error: not_found}), the DE-only cap with its default of 15 and 0 = all, AT ignoring that parameter, and the critical caveat that financials.reporting_status distinguishes 'no data published' from 'not processed' so missing German figures must never be reported as zero.

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: one-line purpose, then parameters, then returns, then a fallback pointer. The opening German sample query and the lengthy returns enumeration cost some density, and the returns detail partly duplicates the existing output schema, but every paragraph is topically organized and serves a reader.

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 two-parameter read tool with an output schema and rich annotations, the definition covers id formats, optional-parameter behavior, the not_found path, country-specific payload differences, and the DE reporting_status trap. An agent could invoke and interpret the result correctly from this text alone.

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 and does: it gives the exact composite id formats with worked examples ('AT:123456a', 'DE:D2601_HRB135076'), notes bare national ids are accepted, and explains max_signatories' default, 0 = all, and AT-only ignoring. Nothing about either parameter is left to guesswork.

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?

Opens with a specific verb + resource + cardinality constraint: 'Full profile for ONE company, routed by its unified id', which immediately separates it from the search/list siblings. The returns block then concretely enumerates what 'profile' means for AT vs DE, so an agent knows exactly what it gets without opening the schema.

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?

Explicitly routes agents that only have a name to search_companies first, and the parameters section says to take company_id from a search card's field, giving a clear task flow into this tool. It stops short of stating when NOT to use it (e.g. versus get_full_record / get_company_history, which sound adjacent), so no full exclusion set.

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

All Firmenbuch 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