Skip to main content
Glama
jkbngb

agentic-firmenbuch

by jkbngb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Full company record

get_full_record
Read-onlyIdempotent

Retrieve a company's complete Firmenbuch record by Firmenbuchnummer, including full per-year position history, unknown-code passthrough, completeness flags, and lineage. Use for completeness audits.

Instructions

Complete per-company record, the full superset we hold for one company. Read-only.

    Parameter:
    - fnr (required): Firmenbuchnummer, e.g. "123456a" (the `fnr` from a search card).

    Returns everything: every position's full per-year history, unknown-code passthrough
    (nothing dropped), completeness flags, guv_years, and lineage (§5.1). This is the heaviest
    read. Use it when you need raw completeness; for the normal curated profile use
    get_company_details, for a single metric's trend use get_company_history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fnrYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/destructive=false, so the safety profile is handled. The description adds genuine behavioral context beyond that: it is 'the heaviest read', it passes through unknown codes ('nothing dropped'), and it includes completeness flags, guv_years and lineage. It does not mention rate limits or result size/pagination.

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 with the identity of the tool, then the parameter, then the return contents and routing. Every sentence earns its place; no filler.

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 one-parameter read tool with an output schema present, the description supplies everything needed: what it does, the parameter's meaning/format, what comes back at a high level, and when to prefer siblings. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 burden. It explains that fnr is the Firmenbuchnummer, gives a concrete format example ('123456a'), and tells the agent its source (the fnr from a search card). That is meaningful added semantics for the single required parameter.

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: 'Complete per-company record, the full superset we hold for one company.' It defines the scope (everything for one company) and explicitly distinguishes itself from get_company_details and get_company_history by naming both siblings.

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: 'Use it when you need raw completeness; for the normal curated profile use get_company_details, for a single metric's trend use get_company_history.' Both alternatives and their selecting conditions are named.

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