Skip to main content
Glama
Sign In

tropia.pl: Polish companies (KRS)

by pl.tropia
OverviewDiscussionsAdmin

Financial summary by year

get_financials
Read-onlyIdempotent

Multi-year financial summary of a company from statements filed in KRS (eKRS financial documents repository): revenue, net profit, total assets, equity per year, in PLN. Cost: 0.03 PLN.

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_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsYesKRS number (Polish National Court Register), up to 10 digits, e.g. "0000028860". Get it from search_companies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuinely new traits: the data source (eKRS repository), the currency (PLN), and critically that the call is paid (0.03 PLN) — cost is not captured in annotations.

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 short sentences, front-loaded with what is returned via a colon-delimited field list, followed by the cost. Nothing is padded and every clause carries 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?

With no output schema, the description correctly enumerates the return fields and units, which is the key missing piece. It does not state how many years are covered or what happens when no filings exist, minor gaps for a single-parameter read tool.

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%: the single 'krs' parameter already documents its format, pattern, example, and where to obtain it. The description adds only that the data originates from KRS filings, which is marginal beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (multi-year financial summary from KRS filings) and enumerates the returned fields (revenue, net profit, total assets, equity per year) plus currency. It implicitly separates itself from the singular get_financial_statement via 'summary', but never names or contrasts that sibling, so an agent must infer the distinction.

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

Usage Guidelines2/5

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

No explicit when-to-use, prerequisites, or alternatives are given. The near-identical sibling get_financial_statement makes routing guidance especially valuable here, and its absence leaves the agent to guess which tool to call.

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

All tropia.pl: Polish companies (KRS) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources