Skip to main content
Glama
Sign In

skanfirmy.pl

by io.github.bartosz-kuc
OverviewDiscussionsAdmin

szukaj_katalog_api

Read-onlyIdempotent

Search otwarteAPI.pl, a catalog of public Polish and EU APIs (VAT, KRS, GUS, NBP, ECB, Eurostat and more). Returns matching entries with a link to each API's official docs. An empty query returns the whole catalog (optionally narrowed by scope or topic).

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

Input Schema

NameRequiredDescriptionDefault
tematNoNarrow to a specific catalog tag, e.g. "firmy" or "dane-statystyczne". Optional.
zasiegNoNarrow to Polish (PL) or EU APIs. Optional.
zapytanieNoNatural-language query, e.g. "euro exchange rate" or "weather data". Optional.

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, repeatable read. The description adds behavior beyond the annotations by explaining the return shape (matching entries plus a link to each API's official docs) and the empty-query fallback. It does not mention result limits or pagination.

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?

The description is three tight sentences. It front-loads what the tool is and what it returns, and it saves the empty-query edge case for last. 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 simple, three-optional-parameter search tool with fully annotated safety semantics, the description covers purpose, coverage domain, and return content. The only minor gaps are result-set size limits and sorting, which an agent might want to know before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds meaning beyond the schema by stating that all parameters are optional, that omitting them returns the entire catalog, and that the query is a natural-language string. It does not give examples of valid topic tags beyond those in the schema.

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?

The description uses a specific verb and resource: 'Search otwarteAPI.pl, a catalog of public Polish and EU APIs', and names concrete contents (VAT, KRS, GUS, NBP, ECB, Eurostat). This lets an agent tell a catalog search apart from the sibling lookup tools. It does not explicitly name which sibling to use instead.

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?

The description says that an empty query returns the whole catalog, optionally narrowed by scope or topic, which explains how to use the tool with no parameters. It does not say when to call this tool instead of the specific lookup tools such as sprawdz_nip or sprawdz_regon.

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

All skanfirmy.pl 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