Skip to main content
Glama

Dane Gov Pl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Institutions

search_institutions
Read-onlyIdempotent

Search/list data-publishing institutions (ministries, agencies, municipalities, companies) on dane.gov.pl. Returns JSON:API institution objects with id, title, abbreviation, institution_type, website, regon and dataset count. Mostly Polish content; q accepts Polish or English.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query (Polish or English), e.g. "ministerstwo".
langNoLanguage hint "en" or "pl".
pageNoPage number (default 1).
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": "ministerstwo"
+  },
+  {
+    "lang": "en",
+    "page": 1,
+    "per_page": 25,
+    "q": "ministry"
+  }
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds that returns JSON:API objects with specific fields and 'mostly Polish content', which enriches context beyond annotations.

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 concise sentences, front-loaded with purpose and result. Every sentence adds value with no redundancy or fluff.

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?

Given rich annotations and full schema coverage, description fully informs about purpose, return type, and content context (Polish). Pagination details are in schema, so completeness is high.

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 covers all 4 parameters with descriptions (100% coverage). Description adds no per-parameter meaning beyond noting q accepts Polish or English, already in schema. Baseline of 3 is appropriate.

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?

Description clearly states verb 'search/list' and resource 'institutions' with specific example types (ministries, agencies, etc.). Distinguishes from sibling tools like search_datasets indirectly, but lacks explicit differentiation.

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?

Implies usage for searching Polish institutions with language hint, but no explicit when-not-to-use or alternatives like search_datasets. Guidance is minimal.

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