Skip to main content
Glama
jkbngb

agentic-firmenbuch

by jkbngb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Download annual filing

get_document
Read-onlyIdempotent

Fetches a signed, 15-minute download link to a company's official Jahresabschluss PDF from the Austrian register. Use for original filings; parsed figures are available via other tools.

Instructions

Get a time-limited download link to a company's official Jahresabschluss document. Read-only.

    Parameter:
    - doc_key (required): a filing's `document_ref` ("{fnr}:{stichtag}") from
      get_company_details, a bare FNR (-> latest filing), or a legacy doc_key.

    Returns `download.url`, a signed link valid for 15 minutes (900 s; the exact expiry is
    `download.expires_at` / `expires_in_seconds` in the response — open it promptly, don't
    expect bytes inline), plus the `financial_institution` flag + caveat for banks/insurers,
    whose figures live only in the PDF. If the PDF is not in the archive yet it is fetched
    on demand from the register (the first call for a year can take up to ~1 minute);
    `download` is null only when the register itself holds no document for that filing. Use to
    fetch the original filing artifact; for the already-parsed figures use
    get_company_details / get_full_record instead of downloading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Read-only is already in annotations, but the description adds real behavioral context the annotations don't: 15-minute (900 s) signed-link expiry, the ~1 minute on-demand fetch from the register for the first call of a year, the financial_institution flag/caveat for banks and insurers, and the precise condition under which download is null (register holds no document).

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 action, then parameter, then return semantics; nearly every sentence earns its place. It does re-enumerate output field names (download.url, expires_at, expires_in_seconds) that the output schema already carries, which is mild redundancy, but the accompanying expiry/latency semantics justify it.

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?

Given a one-parameter tool with an output schema and full annotations, the description supplies everything an agent needs: key format, the expiry window, the latency and null cases, the bank/insurer caveat, and the alternative tools. Nothing material 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?

Schema coverage is 0% and the single parameter is undocumented in the schema, so the description carries the full burden — and does: doc_key accepts a document_ref formatted '{fnr}:{stichtag}' from get_company_details, a bare FNR (meaning latest filing), or a legacy doc_key. That is exactly the syntax an agent needs.

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 first sentence states a precise verb+resource+output: it returns a time-limited download link to a company's official Jahresabschluss. It also draws the line against get_company_details / get_full_record for already-parsed figures, so an agent can separate it from the parsing siblings without opening schemas.

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?

Explicit routing: 'Use to fetch the original filing artifact; for the already-parsed figures use get_company_details / get_full_record instead of downloading.' Plus an operational warning to open the link promptly rather than expect inline bytes. Clear when-to-use and named alternatives.

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

Deploy Server

Other Tools