Skip to main content
Glama

Get Company Profile

get_company
Read-onlyIdempotent

Get the registry profile of one Polish company: name, legal form, address, industry (PKD), share capital, representation rules, recent registry changes, VAT status and headline financials for the latest filed period. Identify the company by name, KRS number or company tax number (NIP). For earlier years or full statements use get_financials.

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": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsNoKRS number of the company in the Polish National Court Register (10 digits).
nipNoPolish company tax number (NIP) of the business, 10 digits.
langNoLanguage of `company_summary` (default pl). Falls back to en, pl, de when missing.
nameNoCompany name, used when the KRS or NIP is not known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Language of `company_summary` (default pl). Falls back to en, pl, de when missing.",
      +  "enum": [
      +    "pl",
      +    "en",
      +    "de"
      +  ],
      +  "type": "string"
      +}
  2. 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 behavior, so the description adds the scope detail that matters: which fields are returned, that financials are headline-only for the latest filed period, and where deeper history lives. It does not state identifier precedence or failure behavior for an unknown company.

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?

Two sentences: the first front-loads the returned profile fields, the second covers identification and routes to the alternative. No redundant restatement of the title or annotations.

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?

For a read-only lookup with a fully documented schema and no output schema, the description covers what is returned, how to identify the company, and where to go for more financial history. The remaining gap is identifier precedence and behavior when a lookup misses.

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 of the four parameters is already documented, including the lang enum and its fallback chain. The description adds only that a company can be identified by any of name, KRS or NIP, without resolving which wins when several are given, so this is the baseline for a fully documented schema.

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 and resource ('registry profile of one Polish company') and enumerates the returned fields: name, legal form, address, PKD industry, share capital, representation rules, recent registry changes, VAT status, financials. It also distinguishes itself from the sibling get_financials for earlier years or full statements.

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?

Explicitly names the alternative tool get_financials and the condition that selects it (earlier years or full statements). It does not say what to do when multiple identifiers are supplied or when nothing is found, but the primary routing guidance is present.

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.