apibase

CZSO Dataset Data

czso.series.dataset_data

Read-onlyIdempotent

Fetch rows from a CZSO dataset's CSV data file (dataset_id from czso.dataset_list). Column names vary per dataset (e.g. "vuzemi_txt" for territory, "rok" for year) — call once without filter_column to see the header, then narrow with filter_column + filter_value (substring match). Rows capped 1-500 (default 50). Datasets whose only resource is not CSV (e.g. ZIP) are rejected with a pointer to the raw download URL. Data: vdb.czso.cz (Czech Statistical Office open-data catalog), no auth required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max rows to return after filtering (1-500, default 50).
`offset`	No	Number of matching rows to skip, for paging through a large filtered result.
`dataset_id`	Yes	CZSO dataset id, from czso.dataset_list (e.g. "130141r25" for 2024 population movement).
`filter_value`	No	Substring to match (case-insensitive) against filter_column's value, e.g. "Praha" when filter_column is "vuzemi_txt". Required when filter_column is set.
`filter_column`	No	Column name to filter on, must match a column in the CSV header returned by this same tool (column names vary per dataset, e.g. "vuzemi_txt" for territory name, "rok" for year, "vuk" for indicator code) — call once without a filter to see the header first. Requires filter_value.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so safety is covered. The description adds substantial behavioral context: row cap (1-500, default 50), substring matching, rejection of non-CSV resources with a fallback pointer, and no auth requirement. This goes well beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but dense with useful information, front-loading the core purpose and then adding operational details. It is not overly verbose and each sentence contributes value. A slightly tighter structure could earn a 5, but the current length is justified.

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 the tool's complexity (5 params, 1 required) and the presence of an output schema (not shown), the description covers all necessary operational aspects: how to get dataset_id, how to discover columns, filtering behavior, row limits, CSV-only restriction, and authentication. No critical information is missing for an agent to invoke it correctly.

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 description coverage is 100%, so all parameters are documented in the schema. The description reinforces the concept of varying column names and the need to discover the header first, but this is already present in the filter_column schema description. No significant additional meaning beyond schema is provided, so baseline 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 states a specific verb and resource: 'Fetch rows from a CZSO dataset's CSV data file.' It clearly differentiates from sibling reference tools by focusing on data retrieval rather than metadata, and it specifies the source of dataset_id via czso.dataset_list. No ambiguity or tautology.

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 provides clear guidance on how to use the tool: call once without filter_column to see the header, then narrow with filter_column and filter_value. It also mentions the CSV-only restriction and points to czso.dataset_list for obtaining dataset_id. It lacks explicit 'when not to use' or direct sibling comparisons, but the context is sufficient for an agent to select this tool appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apibase 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.