agentic-firmenbuch

Overview Schema Source Related Servers Discussions Admin

Company profile

get_company_details

Read-onlyIdempotent

Retrieve a company's full profile from Austria's Firmenbuch by its registration number (FNR). Optionally include specific sections like balance sheet, P&L, ratios, management, events, and industry.

Instructions

Full served profile for one company by FNR. Read-only.

    Parameters:
    - fnr (required): Firmenbuchnummer, e.g. "123456a" (the `fnr` from a search card).
    - include (optional): which optional sections to serve, subset of
      ["bilanz", "guv", "ratios", "management", "events", "industry"]; omit for ALL sections
      (the full profile). Identity, location, company, size, filings and the financials
      scalars (latest values) are always included. Use this to keep the response small when
      you only need part of the profile.
    - history (optional, default true): false drops the per-metric year series (the latest
      values stay) — use get_company_history when you later need a specific trend.

    Null fields are omitted from the response (a missing key means "no data for this
    company"; describe_fields documents every field that CAN exist). Returns one company's
    identity, location, financials (per-year Bilanz + GuV), all computed ratios, growth,
    employees, filings, and management. Use when you already know the company
    (from search_companies); for the complete record (full position taxonomy, unknown-code
    passthrough, per-year lineage) use get_full_record; for specific metric trends use
    get_company_history.
    Field reference: https://www.agentic-firmenbuch.at/felder.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fnr`	Yes
`history`	No
`include`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior (the opening 'Read-only' merely repeats that). The description adds genuinely new traits: null fields are omitted so a missing key means no data, always-included sections, and that history=false drops year series while keeping latest values. Only the return format and size expectations are left thin, which the output schema likely covers.

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 with the identity and read-only statement, then a clean parameter list, then routing guidance. Slightly verbose: the closing sentence re-enumerates the returned sections already listed in the include description ('Identity, location, company, size, filings...'), which is mild redundancy.

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 three-parameter read with annotations and an output schema, this is complete: it covers routing, parameter semantics, null-omission behavior, and even links a field reference for field-level detail. No output-shape explanation is needed given the output schema.

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 must carry all parameter meaning, and it does: fnr format with a concrete example and provenance ('from a search card'), the exact include subset with omit-means-all semantics and its purpose, and history's default plus the effect of setting it false. Nothing about the three parameters is left ambiguous.

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 ('Full served profile for one company by FNR') plus the read-only nature and the lookup key. It explicitly names what it is not (get_full_record for the complete record, get_company_history for trends), so an agent can distinguish it from siblings 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 when-to-use ('when you already know the company, from search_companies') and names two alternative tools with the precise conditions that select them. The include/history guidance adds tactical advice on when to trim the response.

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

Deploy Server