Skip to main content
Glama

Poland company

run_pl_companies
Read-onlyIdempotent

Get one company from the Poland registry (KRS) by KRS number or registry link: name, status, registration date, address, legal form, NIP/REGON, representatives, capital, shareholders, branches, history. Flat 5 points per successful run.

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": {
      "company": "<company>"
    },
    "name": "run_pl_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesKRS number or registry URL. e.g. 0000028860

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already disclose the safe read-only, idempotent, non-destructive profile, so the bar is lower. The description goes beyond them by enumerating the data returned and, notably, disclosing the billing model ('Flat 5 points per successful run'), which is real behavioral context an agent can't get from structured fields.

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 purpose before the billing note. The long comma-separated field list is dense but earns its place given there is no output schema; nothing is redundant.

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 one-parameter lookup with no output schema, the description covers input format, returned data surface, and cost. The only real omission is any routing hint toward run_pl_companies_search or run_pl_company_filings.

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 the single parameter already carries its own description plus an example. The description reinforces the two accepted formats (KRS number or registry URL) but adds no syntax, validation, or normalization detail beyond the 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 ('Get one company from the Poland registry (KRS)') and constrains the scope to a single entity retrieved by KRS number or registry link. Adjacent siblings run_pl_companies_search and run_pl_company_filings are distinguishable from 'one company by KRS number' without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the identifier requirement ('by KRS number or registry link'), so an agent can infer this is the single-entity lookup and that run_pl_companies_search is for lookups without a KRS number. However, no alternative is named and no when-not-to-use condition is given.

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.