Skip to main content
Glama

Firmenbuch

by io.github.jkbngb
OverviewDiscussionsAdmin

Financial history of a company

get_company_history
Read-onlyIdempotent

Beispiel: „Wie hat sich der Umsatz der Rauch Fruchtsäfte GmbH in den letzten fünf Jahren entwickelt?“

Per-year financial-metric history for ONE company, routed by its unified id. Read-only.

    Parameters:
    - company_id (required): "AT:{fnr}" or "DE:{court}_{type}{number}" (bare national ids
      accepted), from a search card.
    - metrics (optional, AT only): names of the metrics to return (e.g. bilanzsumme,
      umsatzerloese, equity_ratio); omitted = all. Ignored for DE.

    Returns the backend's history payload plus ``country`` and the prefixed
    ``company_id``: per-metric {year: value} with latest/latest_year. AT serves the parsed
    Bilanz/GuV/ratio series. DE serves the parsed Jahresabschluss series where the company
    has filed and its Bundesland is loaded; an empty series means not-filed or not-yet-
    loaded, never zero (see get_company_details financials.reporting_status). For a single
    snapshot use get_company_details; for the complete record use get_full_record.

Input Schema

NameRequiredDescriptionDefault
metricsNo
company_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
-}
    • changedInput schema / required
      Previous value: -[
-  "fnr"
-]New value: +[
+  "company_id"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: DE returns an empty series when not-filed or Bundesland not loaded, and explicitly warns that empty never means zero, pointing to financials.reporting_status. That caveat prevents a serious misinterpretation of results.

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 body is dense and well-structured with a compact parameter and return section. The one flaw is the leading German 'Beispiel:' sentence with typographic quotes placed before the purpose statement, which delays front-loading and reads as noise in an otherwise English description.

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?

Even though an output schema exists, the description summarizes the return shape (per-metric {year: value} with latest/latest_year, plus country and prefixed company_id) and explains the country-specific series semantics. Combined with the sibling routing, an agent has everything needed to call and interpret it.

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 coverage is 0%, so the description carries the full burden and does: it gives the exact company_id formats for AT and DE, notes bare national ids are accepted, names the metric identifiers (bilanzsumme, umsatzerloese, equity_ratio), and states that omitted metrics means all and that metrics is ignored for DE.

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 ('Per-year financial-metric history for ONE company') and specifies the routing key ('routed by its unified id'). The capitalized ONE plus the explicit sibling references (get_company_details for a snapshot, get_full_record for the complete record) make it unmistakable against alternatives.

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?

Explicitly routes the agent: single snapshot -> get_company_details, complete record -> get_full_record. It also clarifies country-scoped applicability (metrics is AT only), so the agent knows when this tool will and will not honor a filter.

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