Skip to main content
Glama
jkbngb

agentic-firmenbuch

by jkbngb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Read annual filing text

get_document_text
Read-onlyIdempotent

Reads the full text of a company's official annual financial statement filing, so you can inspect notes, management report, and reported positions directly.

Instructions

Return the TEXT of a company's official Jahresabschluss filing so you can read the Anhang, Lagebericht and positions directly (XML filings are flattened to "label: value" lines, PDF filings are text-extracted). Read-only.

    Parameters:
    - doc_key (required): a filing's `document_ref` ("{fnr}:{stichtag}") from
      list_documents / get_company_details, or a bare FNR (-> latest filing).
    - max_chars (optional, default 40000, max 120000): cap on the returned text;
      `truncated` tells you when the document is longer.

    Use for questions about the wording of a filing ("Was steht im Lagebericht zum
    Ausblick?", "Welche Risiken nennt der Anhang?"). For the parsed figures use
    get_company_details; for a download link use get_document. Cite the Stichtag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_keyYes
max_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered. The description adds genuinely useful format behavior — XML flattened to 'label: value' lines, PDF text-extracted — plus the `truncated` signal. It stops short of permission requirements or error behavior, so a 3 is appropriate for annotations-covered read tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence, then compact parameter block, then usage-and-alternatives block. Every sentence earns its place; the example questions clarify intent rather than pad.

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?

An output schema exists, so return structure need not be explained, and the description still flags the `truncated` field. Combined with thorough parameter documentation and sibling routing, nothing an agent needs to invoke this correctly 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%, so the description carries full burden and does so well: doc_key format ('{fnr}:{stichtag}'), its source tools, and the bare-FNR fallback to the latest filing are all specified. max_chars documents default 40000, max 120000, and the linked `truncated` flag.

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 ('Return the TEXT of a company's official Jahresabschluss filing') and clarifies what content is exposed (Anhang, Lagebericht, positions). It explicitly distinguishes itself from get_company_details (parsed figures) and get_document (download link) without requiring schema inspection.

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?

Provides an explicit when-to-use trigger with example questions ('Was steht im Lagebericht zum Ausblick?') and names the two alternatives with their differing conditions. An agent can route correctly between text reading, figures, and download.

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