Skip to main content
Glama

Prawnet: Polish case law and legislation

Dane spółki z KRS

firma_krs
Read-onlyIdempotent

Firma po jednym z: numer KRS, NIP, REGON, numer VAT UE. Podmiot z KRS (Otwarte API KRS, odpis aktualny, bufor 24 h): nazwa, forma prawna, NIP, REGON, siedziba, kapitał, PKD, postępowania, link do odpisu. Osobne bloki ze źródłem i datą: vat (wykaz podatników VAT MF: status, daty, liczba rachunków na liście, requestId), vies (ważność numeru VAT UE), regon_gus (GUS, wymaga klucza użytkownika). Bez osób fizycznych; dla działalności jednoosobowej tylko status VAT.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firma_krs"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsNoNumer KRS (podaj dokładnie jedno z: krs, nip, regon, vat_ue)
nipNoNIP, 10 cyfr
regonNoREGON, 9 lub 14 cyfr (wyszukiwanie wymaga klucza GUS po stronie serwera)
vat_ueNoNumer VAT UE z prefiksem kraju, np. PL5260251049, DE811128135

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / krs / description
      Previous value: -"Numer KRS"New value: +"Numer KRS (podaj dokładnie jedno z: krs, nip, regon, vat_ue)"
    • changedInput schema / properties / nip / description
      Previous value: -"NIP"New value: +"NIP, 10 cyfr"
    • addedInput schema / properties / regon
      Added value: +{
      +  "description": "REGON, 9 lub 14 cyfr (wyszukiwanie wymaga klucza GUS po stronie serwera)",
      +  "type": "string"
      +}
    • addedInput schema / properties / vat_ue
      Added value: +{
      +  "description": "Numer VAT UE z prefiksem kraju, np. PL5260251049, DE811128135",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/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, so the safety profile is covered; the description goes further by disclosing data provenance (Otwarte API KRS, aktualny odpis), a 24 h cache, per-block source and date stamping, a requestId in the VAT block, and the GUS key requirement. It does not say what happens on lookup failure or a missing GUS key, which is the main remaining behavioral 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?

It is front-loaded with the input identifiers and then the returned blocks, and every clause carries information (sources, cache, limits). The colon-separated noun-phrase style is dense and occasionally telegraphic rather than sentence-based, which costs some readability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the lengthy enumeration of returned fields is somewhat redundant but useful for routing, and the source/cache/key notes are genuinely additive. The remaining gap is error and edge behavior (unknown identifier, missing GUS key, entity not found) and the fact that none of the four parameters is marked required despite the 'exactly one' rule.

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% and each parameter already carries its own description, including the 'exactly one of' rule and the REGON/GUS caveat, so the description largely restates structured data. It does add the framing that the four identifiers are mutually exclusive entry points to the same lookup, but no format or validation detail beyond the schema. 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?

The description names a specific resource (company/entity data) and enumerates the four identifier types accepted (KRS, NIP, REGON, VAT UE), then lists exactly what is returned (name, legal form, NIP, REGON, seat, capital, PKD, proceedings, extract link). Sibling tools are all procedural/case-law tools, so no differentiation is needed and none is missing. An agent can tell instantly this is a registry-lookup tool.

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?

It gives a clear usage constraint ('podaj dokładnie jedno z') and valuable scope exclusions ('Bez osób fizycznych; dla działalności jednoosobowej tylko status VAT'), plus a prerequisite note that the regon_gus block requires a user-supplied GUS key. What it does not do is name an alternative tool or say what to do when the entity is a natural person or when the GUS key is absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources