Skip to main content
Glama

szukaj_api

Read-onlyIdempotent

Przeszukuje otwarteAPI.pl — katalog 92 oficjalnych, publicznych API rządowych z Polski, UE i kilkudziesięciu krajów (rejestry firm, VAT, statystyka, otwarte dane). Zwraca pasujące wpisy z linkiem do oficjalnej dokumentacji, jurysdykcją, typem autoryzacji i formatem. Puste zapytanie zwraca cały katalog (opcjonalnie zawężony filtrami).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaksymalna liczba wyników (1–92, domyślnie 8).
tematNoTag do zawężenia, np. „firmy”, „dane-statystyczne”, „bez-klucza”. Opcjonalne.
zasiegNoKod jurysdykcji do zawężenia, np. PL, EU, DE, GB, US. Opcjonalne.
zapytanieNoZapytanie w naturalnym języku (PL lub EN), np. „sprawdź VAT firmy w Estonii” albo „company register Germany”. Opcjonalne.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maksymalna liczba wyników (1–60, domyślnie 8)."New value: +"Maksymalna liczba wyników (1–92, domyślnie 8)."
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maksymalna liczba wyników (1–53, domyślnie 8)."New value: +"Maksymalna liczba wyników (1–60, domyślnie 8)."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the closed-world hint fits a fixed 92-entry catalog. The description adds behavior the annotations cannot: what each result contains (official documentation link, jurisdiction, auth type, format) and how the empty-query case behaves. It stops short of mentioning result ordering or that the catalog is static, but the added value is real.

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 sentences, densely packed, with the core purpose and corpus scope front-loaded and the empty-query behavior placed last. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe return values — it does, listing the documentation link, jurisdiction, auth type and format per entry. Combined with the catalog size and empty-query semantics, an agent has everything needed to call this correctly.

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 baseline is 3. The description goes slightly beyond the schema by explaining the interaction between 'zapytanie' and the filters: an empty query returns everything, and filters narrow it. It does not add semantics for 'limit' or clarify how natural-language queries are interpreted.

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?

Names a specific verb ('Przeszukuje') and a concrete resource ('katalog 92 oficjalnych, publicznych API rządowych'), and quantifies the corpus and the domains covered (firm registers, VAT, statistics, open data). An agent immediately knows this is a catalog search over a fixed set of government APIs, not a live data fetch.

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 final sentence states the key operational rule: an empty query returns the whole catalog, optionally narrowed by filters — which tells the agent how to browse instead of search. There are no sibling tools to contrast against, so no alternative routing guidance is owed, though it does not state when this tool would be inappropriate.

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