Dane Gov Pl

List Resources

list_resources

Read-onlyIdempotent

List the resources (files/tables) attached to a dataset. Returns JSON:API resource objects with id, title, format (csv/xlsx/...), media_type, link, openness_score and a tabular_data relationship. Resources whose relationships include tabular_data can be read row-by-row with resource_data.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Language hint "en" or "pl".
`page`	No	Page number (default 1).
`per_page`	No	Results per page, 1-100 (default 20).
`dataset_id`	Yes	Dataset numeric id, e.g. "771".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "dataset_id": "771"
+  },
+  {
+    "dataset_id": "771",
+    "lang": "en",
+    "page": 1,
+    "per_page": 50
+  }
+]

First observedMay 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds value by specifying the returned fields and the tabular_data relationship, providing context beyond safety annotations. No contradiction found.

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 concise with two sentences, front-loaded with the main purpose, and includes specific details without unnecessary words. Every sentence adds value.

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?

For a simple list operation with complete schema and annotations, the description covers purpose, return structure, and hints at related tool usage. It is complete enough given the tool's complexity.

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 coverage is 100% with descriptions for all four parameters. The description does not add significant meaning beyond the schema, such as constraints or format. Baseline score 3 is appropriate.

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?

The description uses specific verb 'list' and resource 'resources', clearly distinguishing from sibling tools like 'resource_data'. It specifies the return format with key fields, making the tool's purpose unambiguous.

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 description implies usage by stating what it does and mentions that resources with tabular_data can be read by 'resource_data', offering a hint about alternatives. However, it does not explicitly state when not to use this tool or list other alternatives.

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 tools Inspect

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.