Search otwarteAPI.pl — a catalog of 53 official public Polish and EU APIs (VAT white list, KRS, GUS, NBP, ECB, Eurostat, VIES and more), curated for AI agents. One tool: find the right API by natural-language query. No API key, no signup.
Przeszukuje otwarteAPI.pl — katalog 60 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).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maksymalna liczba wyników (1–60, domyślnie 8). | |
| temat | No | Tag do zawężenia, np. „firmy”, „dane-statystyczne”, „bez-klucza”. Opcjonalne. | |
| zasieg | No | Kod jurysdykcji do zawężenia, np. PL, EU, DE, GB, US. Opcjonalne. | |
| zapytanie | No | Zapytanie w naturalnym języku (PL lub EN), np. „sprawdź VAT firmy w Estonii” albo „company register Germany”. Opcjonalne. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description takes full responsibility for behavior. It discloses the nature of the operation (a search that returns matching entries) and gives meaningful behavior: an empty query returns all catalog entries, optionally narrowed by filters. It does not mention pagination/error specifics, but these would be unimportant for this low-risk read-only search.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, zero fluff. The purpose is front-loaded, followed by what is returned and the key edge-case (empty query). Every sentence contributes to an agent's decision.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a medium-low complexity tool with only optional params and no output schema, the description gives enough context: a purpose, params, it behavior on empty input, and the shape of each result entry. A few minor details on output shape and no results handling would be nice, but nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: all 4 params have clear descriptions with types, examples, and defaults. The description also adds a behavior beyond the schema: that 'empty query returns the whole catalog (optionally filtered)', clarifying the relationship between the query parameter and the filter params'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description starts with a precise verb ('Przeszukuje') and names the exact resource (otwarteAPI.pl — a catalog of 60 public government APIs). It also enumerates the returned fields (documentation link, jurisdiction, authorization type, format), making the tool's responsibility unmistakable even without sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It doesn't explicit state 'use when X, not for Y', but it provides clear context in which the tool should be used: looking for official public APIs from Poland/EU/etc with natural language or filters. The empty-query behavior is an additional usage hint (for listing the whole catalog). A sinnce no sibling exists, the bar for exclusions is naturally relaxed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
szukaj_api1 field changedInput schema / properties / limit / descriptionPrevious value: -"Maksymalna liczba wyników (1–53, domyślnie 8)."New value: +"Maksymalna liczba wyników (1–60, domyślnie 8)."szukaj_apiClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
There is only one tool, so there is no possibility of overlapping purposes or misselecting between tools. The tool's single responsibility is clearly defined.
The single tool name, szukaj_api, uses a readable verb_noun structure and is not inconsistent with anything else. However, with only one tool there is no real naming pattern to evaluate.
A one-tool server feels thin, but the tool is not trivial: it supports searching, filtering, and returning the full directory. Still, the server offers only a minimal read-only surface.
For a directory search server, one search tool that can list the whole catalog and return metadata covers the core need. Minor functionality such as pagination or category-level browsing may be missing, but no dead end is evident.