Skip to main content
Glama

Search the KRS registry

search_companies
Read-only

Search Polish companies in the KRS by name, KRS, NIP, or REGON to find matching entities and resolve a company name to its 10-digit KRS number before retrieving full registry details.

Instructions

Search Polish companies in the KRS (National Court Register) by name or partial name ("query"), KRS, NIP or REGON. Returns matching entities with their padded 10-digit KRS numbers — use this FIRST to resolve a company name to a KRS number before calling get_company / get_company_full / get_board.

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

Input Schema

NameRequiredDescriptionDefault
krsNoExact KRS number, 1-10 digits.
nipNoExact NIP number, 10 digits.
nameNoAlias for query.
pageNo
nazwaNoAlias for query.
queryNoCompany name or partial name. This is the only tool that can resolve a company NAME to a KRS number.
regonNoExact REGON number, 9 or 14 digits.
pageSizeNo
registriesNoRegistries to search: P = entrepreneurs, S = associations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds that results come back with padded 10-digit KRS numbers and that this is the only tool able to convert a name into a KRS number. It does not mention pagination behavior (pageSize capped at 100), empty-result behavior for open-world lookups, or filtering by the registries array, leaving some behavioral gaps.

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 tight sentences, front-loaded with the search scope and the returned identifier, followed by the sequencing instruction. No redundant restatement of the title or name, and every clause carries actionable information.

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 9-parameter, no-output-schema search tool, the description covers purpose, accepted identifiers, return shape and call ordering. Minor omissions are pagination expectations and the meaning of the registries P/S split, both of which the schema partly covers.

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 78%, so the schema already documents most parameters including the name/nazwa aliases, defaults and patterns. The description reinforces that query accepts a partial name and is the sole name-to-KRS resolver, but adds nothing about page/pageSize paging or the P/S registries filter beyond what the schema states.

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 (search Polish companies in the KRS registry) plus the identifier types accepted (name/partial name, KRS, NIP, REGON). It also signals the return shape (matching entities with padded 10-digit KRS numbers), so an agent can distinguish it from get_company / get_company_full / get_board without opening a 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?

Explicitly tells the agent to use this FIRST to resolve a company name to a KRS number before calling get_company, get_company_full or get_board — a concrete when-to-use rule with named alternatives and an ordering constraint. This is exactly the routing guidance that prevents an agent from calling the detail tools with an unresolvable name.

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