Skip to main content
Glama

Dane Gov Pl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Datasets

search_datasets
Read-onlyIdempotent

Search/list datasets on Poland's national open data portal (dane.gov.pl). Returns a JSON:API list of datasets with id, title, notes, slug, institution and resource count. Content is mostly Polish; q accepts Polish or English. Use the returned dataset id with dataset_details / list_resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query (Polish or English), e.g. "budżet", "health", "powietrze".
langNoLanguage hint "en" or "pl"; only some portal fields are translated.
pageNoPage number (default 1).
sortNoSort field, e.g. "id", "-created", "title". Default "id".
per_pageNoResults per page, 1-100 (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "q": "budżet"
+  },
+  {
+    "lang": "en",
+    "page": 1,
+    "per_page": 50,
+    "q": "air quality",
+    "sort": "-created"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive; description adds value by specifying return format (JSON:API list), language hints, and linkage to other tools.

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, front-loaded with purpose and output, followed by usage guidance; no wasted words.

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?

Description compensates for missing output schema by listing return fields; covers pagination and sorting implicitly through parameters; adequate for a simple search tool.

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 has 100% coverage with detailed descriptions; description adds minimal extra meaning beyond mentioning portal context and language acceptance.

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?

Description clearly states it searches/lists datasets on Poland's national open data portal, returns specific fields, and distinguishes from sibling tools like dataset_details and list_resources.

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?

Provides context on language (Polish/English), portal origin, and links to related tools for specific dataset details, but doesn't explicitly state 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.

All Dane Gov 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