Skip to main content
Glama
Skeego

opendata-mcp

by Skeego

get_subdataset_by_path_v1_datasets__provider___dataset___subdata

Retrieve subdataset metadata and paginated data rows. Use cursor for efficient keyset pagination and optional parameters to filter, sort, or group.

Instructions

GET /v1/datasets/{provider}/{dataset}/{subdataset} (public) — Get Subdataset By Path — Get subdataset with inline data.

Returns subdataset metadata with paginated data rows.

Pagination:

  • Use cursor for keyset pagination (efficient for large datasets with views)

  • The response includes next_cursor if more data is available

  • Pass the next_cursor value as cursor in the next request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYes
datasetYes
subdatasetYes
limitNo
offsetNo
cursorNoCursor for keyset pagination (from next_cursor in previous response)
viewNoView: 'flat', 'timeseries', or custom grouping params
expandNoComma-separated fields to expand (e.g., 'area,item')
fieldsNoComma-separated columns to include (e.g., 'date,value')
sortNoColumn to sort by. Prefix with - for descending (e.g., 'date', '-year')
group_byNoColumn to group by
nest_fieldsNoComma-separated columns to include in nested items
nest_fieldNoName for nested array (default: 'items')
sort_nestedNoColumn to sort nested items by
aggregateNoComma-separated aggregate expressions: avg(score),count(*). Supported functions: count, sum, avg, min, max, count_distinct
include_sourcesNoInclude source attribution columns in response data
response_formatNoResponse format: 'columnar' (default, compact array-of-arrays) or 'objects' (array-of-dicts)
debugNoInclude debug info (query echo, generated SQL) in response
Behavior4/5

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

With no annotations, description discloses pagination mechanism (cursor, next_cursor) and states it's public. It mentions efficiency of keyset pagination. However, it does not discuss error handling, rate limits, or response structure beyond data rows.

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?

Description is extremely concise: four sentences, front-loaded with purpose, followed by essential pagination details. No redundant or irrelevant information.

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?

For a GET data retrieval tool with 18 params and no output schema, the description covers retrieval and pagination adequately. However, it lacks details about response structure and does not differentiate from sibling tools, missing some completeness.

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 72%, so baseline is 3. Description adds value by explaining pagination behavior for cursor, but other parameters are not enhanced. The cursor description in schema is already comprehensive.

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 clearly states the action ('Get subdataset with inline data') and resource (subdataset by path). It distinguishes from siblings by specifying it returns data rows, not just metadata.

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?

Description provides pagination guidance but does not explicitly state when to use this tool vs alternatives like get_subdataset_meta (metadata only) or get_dataset_by_path. No when-not or explicit sibling differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Skeego/opendata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server