Skip to main content
Glama

Handelsregister

by io.github.jkbngb
OverviewDiscussionsAdmin

Financial history of a company

get_company_history
Read-onlyIdempotent

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. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile, but the description adds behavior beyond them: empty DE series means 'not-filed or not-yet-loaded, never zero', AT vs DE backend differences, and metrics being ignored for DE. These are non-obvious operational facts an agent could not infer from annotations or schema.

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?

Well front-loaded with purpose, then clearly sectioned Parameters and Returns blocks; every line is information-dense. Minor ding: the standalone 'Read-only.' sentence repeats readOnlyHint from annotations, adding no new information.

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 backend-varying tool with 2 params, coverage is complete: id formats, metric filtering, payload shape (per-metric {year: value} plus country/prefixed id), and sibling routing are all present. The output schema exists, yet the description still adds the AT/DE interpretation nuance an agent needs.

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 defines the company_id formats ('AT:{fnr}', 'DE:{court}_{type}{number}', bare national ids accepted) and the metrics parameter (optional, AT-only, example metric names, omitted = all). This fully compensates for the empty schema.

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+resource+scope ('Per-year financial-metric history for ONE company'), and explicitly routes to siblings get_company_details (single snapshot) and get_full_record (complete record). An agent can distinguish it from every sibling without opening a schema.

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?

Gives explicit routing rules: use get_company_details for a snapshot, get_full_record for the complete record. It also states a condition on a parameter ('metrics optional, AT only... Ignored for DE'), so both when-to-use and edge conditions are 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