Skip to main content
Glama

AnalizaFirm.pl - Polish companies (KRS)

Komplet danych firmy

firma
Read-onlyIdempotent

Komplet danych spółki z KRS: dane rejestrowe, PKD, kapitał, zarząd i wspólnicy, ocena kondycji A–E (scoring), finanse do 10 lat z wskaźnikami, limit kredytu kupieckiego (kredyt_kupiecki), historia złożeń sprawozdań, postępowania w KRZ, Biała lista VAT z rachunkami, fakty z informacji dodatkowej, szacunkowa wycena. Kwoty w PLN. Zużywa 1 z puli na firmę w ciągu 24 h; kolejne wywołania dla tej samej firmy w tej dobie (także finanse, sprawozdanie, crbr) są bezpłatne. Podaj krs albo nip.

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

Input Schema

NameRequiredDescriptionDefault
krsNoNumer KRS (do 10 cyfr, np. 0000028860)
nipNoNIP (10 cyfr), gdy nie znasz KRS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 closed-world scope, so the safety profile is covered. The description adds genuinely non-annotated behavior: a per-company daily quota consumed by this call, the 24-hour free window covering related tools, and that all monetary amounts are in PLN. It does not cover failure modes such as supplying neither or both identifiers.

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?

The output inventory is front-loaded in the first sentence, followed by the two operationally important facts (PLN currency, quota/free-window rule) and the invocation hint. The enumeration is dense but each item maps to a real data block an agent may need to reason about; no filler sentences.

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 broad aggregator tool with no output schema, listing every returned data category is exactly the right compensation, and the quota rule prevents wasteful re-calling. Remaining gaps are minor: no statement on which identifier wins if both are given, and no indication of response shape or latency for such a large payload.

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% and both parameters are documented in-schema (KRS up to 10 digits with example, NIP when KRS unknown), so the baseline is 3. The description's only addition is "Podaj krs albo nip", which lightly signals the either/or relationship but largely restates 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 the specific resource ("Komplet danych spółki z KRS") and enumerates the exact data bundles returned: registration data, PKD, capital, management/shareholders, A–E scoring, up to 10 years of financials with indicators, trade credit limit, filing history, KRZ proceedings, VAT whitelist, notes facts, and a valuation estimate. It also distinguishes itself from siblings by naming finanse, sprawozdanie, and crbr as free follow-ups once this call has been made.

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?

The quota economics ("Zużywa 1 z puli na firmę w ciągu 24 h"; subsequent same-day calls to firma/finanse/sprawozdanie/crbr are free) give a clear implicit rule: call firma first, then use the narrower siblings. It also says how to invoke ("Podaj krs albo nip"). What is missing is explicit negative guidance, e.g. use szukaj_firmy when the KRS is unknown, or skip firma when only one data block is needed.

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.

Resources