Skip to main content
Glama

run_pl_company_filings

Retrieve filed financial documents and registry entries for a Polish company (KRS) by KRS number or URL, newest first, with dates, types, periods, and details.

Instructions

List the filed financial documents (annual and consolidated statements, auditor opinions, approval resolutions, management reports) and register entries of a Poland company (KRS) by KRS number or registry link, newest first: date, type, period and entry details. 1 point per returned record.

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

Input Schema

NameRequiredDescriptionDefault
companyYesKRS number or registry URL. e.g. 0000635012
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses ordering ('newest first'), the returned fields ('date, type, period and entry details'), and cost ('1 point per returned record'). It omits auth/permission requirements and pagination behavior, which is a modest gap for a read tool.

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?

Purpose and identifier are front-loaded in a single dense sentence, with a short trailing note on cost. The document-type parenthetical is useful specificity rather than padding, though the sentence is long.

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?

Given no output schema and no annotations, the description supplies the essentials an agent needs: what is returned, the sort order, and the cost. Pagination limits live in the schema, so the remaining gap is small.

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 description coverage is 100%, so both the company identifier format and the max_items/start_page bounds are already documented in the schema. The description's 'by KRS number or registry link' merely restates the schema's 'KRS number or registry URL', and it says nothing about max_items or start_page.

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 ('List') and resource ('filed financial documents ... and register entries of a Poland company (KRS)'), enumerated with concrete document types. It clearly distinguishes this country-specific filings tool from siblings like run_pl_companies and run_pl_companies_search.

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?

Gives clear context: it is the tool for filings/register entries of a Polish company, queried by KRS number or registry link. However, it never explicitly contrasts itself with run_pl_companies_search or other country filings tools, nor states when NOT to use it.

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

Deploy Server

Other Tools