Skip to main content
Glama

Overfit — German tenders & procurement law

by de.overfit
OverviewDiscussionsAdmin

Firmenprofil

firma_profil
Read-onlyIdempotent

Register profile of one German company from the Overfit dataset: name, address, legal form, register court, WZ industry code, website and alive verdict (active/dead/unknown) with the date of the status (as_of). No account or key required. Example user questions: 'Wer steckt hinter HRB 52093, Amtsgericht Hamburg?' (key K1101_HRB52093), 'Welche Adresse hat K1101_HRB52093?', 'Is this company still active?' Related: firma_status checks up to 25 companies at once; firma_finanzen returns the financial history; vergabe_suche finds tenders by topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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).

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.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, yet the description adds real value: no account or key required, and explicit error semantics ('invalid format' vs 'not found', usually a wrong court code). It does not describe response shape, but with no output schema that is a minor gap.

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 purpose and return fields, then examples, then related tools. Dense but every sentence carries routing or key-format information; slightly long due to three example questions that could be trimmed to two.

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 single-param, no-output-schema read tool, the description covers what is returned, auth requirements, error outcomes, and sibling routing. An agent has everything needed to select and invoke it correctly.

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 100% and the schema itself already documents format, derivation source, and error behavior, so baseline is 3. The description adds a little by anchoring the key format with the concrete example 'K1101_HRB52093' tied to user questions, aiding natural-language-to-key mapping.

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 ('Register profile of one German company') and enumerates the exact returned fields (name, address, legal form, register court, WZ code, website, alive verdict with as_of). It is immediately distinguishable from firma_status (bulk) and firma_finanzen (financial history), which are named.

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?

Explicitly routes among alternatives: 'firma_status checks up to 25 companies at once' (bulk), 'firma_finanzen returns the financial history', 'vergabe_suche finds tenders by topic'. This gives an agent clear conditions for choosing this single-company tool versus its 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