Skip to main content
Glama

finwire.pl - Polish financial data

New companies in Poland (KRS and CEIDG)

get_new_companies
Read-onlyIdempotent

Use for how many new companies (sp. z o.o., S.A., partnerships) are registered in KRS each month and for all new firms in Poland together with sole proprietorships. For closures and suspensions of sole proprietorships, use get_business_registrations. New commercial companies entered in the Polish National Court Register (KRS) each month by legal form (limited liability, simple joint-stock, joint-stock, partnerships), counted by finwire.pl from the Ministry of Justice KRS API (daily bulletin and current extracts), with applications to register a sole proprietorship in CEIDG (MRiT) for the same month, the share of companies among new firms, the current month so far against the same days a year earlier and the finwire index finwire_new_companies_pulse (new sole proprietorships plus new companies, % year on year).

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

Input Schema

NameRequiredDescriptionDefault
historyNoNumber of past months in the summary, default 12.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds real context beyond that: data provenance (Ministry of Justice KRS API daily bulletin and current extracts, CEIDG/MRiT), the counting basis, and the fact that the current month is partial and compared against the same days a year earlier. It does not discuss latency, rate limits, or backfill behavior, which keeps it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing information is correctly front-loaded in the first sentence. However, the second sentence is a ~90-word run-on that stacks provider names, legal-form enumerations, and the index identifier, several of which (e.g. 'finwire index finwire_new_companies_pulse') read as internal naming rather than agent-facing guidance.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers purpose, the sibling boundary, data sources, and the partial-current-month caveat. What remains thin is the single tunable parameter and any sense of data freshness/update cadence.

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 'history' parameter (0-60, default 12) is fully documented in the schema, so the baseline of 3 applies. The description never mentions the history window or that the output is a month-series summary whose depth is configurable, so it adds no meaning 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?

The description names a concrete verb+resource: monthly counts of new commercial companies entered in KRS by legal form, plus CEIDG sole proprietorships, plus a derived pulse index. It also explicitly separates this from get_business_registrations (closures/suspensions), so an agent can distinguish the two 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?

It opens with an explicit 'Use for ...' framing and then gives a when-not clause naming the alternative tool and the condition that selects it ('For closures and suspensions of sole proprietorships, use get_business_registrations'). Nothing about selection is left to inference.

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.