Skip to main content
Glama

Get full KRS extract

get_company_full
Read-only

Fetch the full official JSON extract of a Polish company from the KRS registry by KRS number, preserving historical entries when registry history is needed.

Instructions

Fetch the FULL (pelny) official semantic JSON extract of a Polish company from the KRS registry by its 1-10 digit KRS number. Preserves all historical entries. Much larger than the current extract; use get_company unless history is needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "krs": "<krs>"
    },
    "name": "get_company_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsYesKRS number, 1-10 digits (padding is applied automatically).
rejestrNoRegistry: P = entrepreneurs, S = associations.P

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuine behavioral context by saying all historical entries are preserved and the payload is much larger than the current extract. It stops short of describing response shape, size magnitude, or any rate/pagination behavior, which keeps it from a 5.

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?

Two sentences, front-loaded with the operation and scope, then the alternative. Minor redundancy in repeating the 1-10 digit KRS constraint already present in the name, schema pattern, and schema description.

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?

Covers selection, scope, and the key tradeoff (size vs. history) for a two-parameter read-only tool with no output schema. What an agent needs in order to choose and call it is present; only return-value or payload-size expectations are left implicit.

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 description coverage is 100%, so both krs and rejestr are already documented, including the padding behavior. The description restates the 1-10 digit constraint already encoded in the pattern and adds nothing about rejestr semantics, so it meets but does not exceed the baseline.

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 (Fetch) and a precisely scoped resource: the FULL official semantic JSON extract of a Polish company from the KRS registry, keyed by KRS number. It also explicitly contrasts itself with get_company, so an agent can distinguish it from a sibling without opening either schema.

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 an explicit routing rule: 'use get_company unless history is needed', naming the alternative and the condition that selects it. It also flags size ('Much larger than the current extract') as a reason to prefer the lighter tool, which is actionable guidance.

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