Skip to main content
Glama

Overfit — German tenders & procurement law

by de.overfit
OverviewDiscussionsAdmin

Bilanzentwicklung einer Firma

firma_finanzen
Read-onlyIdempotent

Financial history of a German company from its filed annual accounts, one row per fiscal year: Bilanzsumme, Eigenkapital, Jahresüberschuss, Umsatz, Mitarbeiter, from the Overfit dataset. Small companies may legally omit revenue (shown as not published). NULL means the figure was not published (not zero). No account or key required. Example user questions: 'What were the revenues of K1101_HRB52093 (HRB 52093, Amtsgericht Hamburg) in 2022?', 'Show me the equity history of this company'. The alive status alone comes from firma_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_yearNoMost recent fiscal year to include (e.g. 2023). Optional.
registerYescompany_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, Example: 'K1101_HRB52093' is HRB 52093 at Amtsgericht Hamburg (court code K1101). Court codes are not derivable from city names or initials; the key comes from firma_finden (register number + court, EUID, LEI, VAT ID) or from an earlier firm tool result. Errors: input that is not a key (e.g. 'Hamburg HRB 52093') is answered 'invalid format' while firma_finden is unavailable (afterwards such input is resolved like in firma_finden); a well-formed key that belongs to no company is answered 'not found' (usually a wrong court code).
from_yearNoOldest fiscal year to include (e.g. 2018). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / register / description
      Previous value: -"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, Example: 'K1101_HRB52093' is HRB 52093 at Amtsgericht Hamburg (court code K1101). Court codes cannot be derived from city names or initials — never guess them; use firma_finden (register number + court, EUID, LEI, VAT ID), or a key returned by an earlier firm tool result. Errors: input that is not a key (e.g. 'Hamburg HRB 52093') is answered 'invalid format' while firma_finden is unavailable (afterwards such input is resolved like in firma_finden); a well-formed key that belongs to no company is answered 'not found' (usually a wrong court code)."New value: +"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, Example: 'K1101_HRB52093' is HRB 52093 at Amtsgericht Hamburg (court code K1101). Court codes are not derivable from city names or initials; the key comes from firma_finden (register number + court, EUID, LEI, VAT ID) or from an earlier firm tool result. Errors: input that is not a key (e.g. 'Hamburg HRB 52093') is answered 'invalid format' while firma_finden is unavailable (afterwards such input is resolved like in firma_finden); a well-formed key that belongs to no company is answered 'not found' (usually a wrong court code)."
  2. Changed1 schema field changed
    • changedInput schema / properties / register / description
      Previous value: -"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, e.g. 'K1101_HRB52093'. The court segment (K1101) is the court code of the company's EUID — use the norm returned by a prior firm tool call (firma_finden, firma_profil, firma_status). Do NOT provide a plain court name like 'Hamburg HRB 12345': the tool will return a format error."New value: +"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, Example: 'K1101_HRB52093' is HRB 52093 at Amtsgericht Hamburg (court code K1101). Court codes cannot be derived from city names or initials — never guess them; use firma_finden (register number + court, EUID, LEI, VAT ID), or a key returned by an earlier firm tool result. Errors: input that is not a key (e.g. 'Hamburg HRB 52093') is answered 'invalid format' while firma_finden is unavailable (afterwards such input is resolved like in firma_finden); a well-formed key that belongs to no company is answered 'not found' (usually a wrong court code)."
  3. Changed1 schema field changed
    • changedInput schema / properties / register / description
      Previous value: -"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, e.g. 'K1101_HRB52093'. The court segment (K1101) is the EUID code assigned by the Unternehmensregister — use the norm returned by a prior firma_profil call or from unternehmensregister.de. Do NOT provide a plain court name like 'Hamburg HRB 12345': the tool will return a format error."New value: +"company_number_norm — the unique register key for a German company. Format: {CourtLetter}{4digits}_{HRB|HRA|PR|GnR|VR}{Nummer}, e.g. 'K1101_HRB52093'. The court segment (K1101) is the court code of the company's EUID — use the norm returned by a prior firm tool call (firma_finden, firma_profil, firma_status). Do NOT provide a plain court name like 'Hamburg HRB 12345': the tool will return a format error."
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely useful context beyond them: the Overfit dataset source, that NULL means 'not published' rather than zero, that small companies may legally omit revenue, and that no account or key is required. It does not mention rate limits or pagination, but no such concern is implied here.

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 core purpose and returned fields, then edge cases (NULL, omitted revenue), then examples. Every sentence is informative, though the two long example questions and the firma_status aside make it slightly heavier than necessary.

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?

With no output schema, the description carries the full burden of explaining the return shape, and it does: it names the columns, explains the row granularity (one per fiscal year), and clarifies NULL semantics and legal omission of revenue. An agent has everything needed to interpret results correctly.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so register/to_year/from_year are fully documented in the schema, including the error semantics ('invalid format', 'not found') and the format of the register key. The description adds only the 'no account or key required' note, which is not parameter-level detail, so the baseline 3 applies.

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: the financial history of a German company from filed annual accounts, one row per fiscal year, and enumerates the returned fields (Bilanzsumme, Eigenkapital, Jahresüberschuss, Umsatz, Mitarbeiter). It also explicitly carves out the sibling boundary: 'The alive status alone comes from firma_status.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger examples ('What were the revenues of K1101_HRB52093 in 2022?') and directs the agent to firma_finden / earlier firm tool results as the source of the register key. It names firma_status as the alternative for status-only questions, but does not systematically cover when-not-to-use or other firm_* siblings.

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

All Overfit — German tenders & procurement law 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