Skip to main content
Glama
Skeego

opendata-mcp

by Skeego

get_dataset_by_path_v1_datasets__provider___dataset__get

Fetch dataset data or subdataset list by specifying provider and dataset path. Supports pagination, format selection, sorting, grouping, and aggregation.

Instructions

GET /v1/datasets/{provider}/{dataset} (public) — Get Dataset By Path — Get dataset data (flat) or subdataset list (hierarchical).

For flat datasets: Returns paginated data with full query support. For hierarchical datasets: Returns list of subdatasets.

Metadata is available at GET /v1/datasets/{provider}/{dataset}/meta

Format Selection (in priority order):

  1. Accept header: application/json, text/csv, text/tab-separated-values, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, application/vnd.apache.parquet

  2. ?format query param: json, csv, tsv, xlsx, parquet

csv/tsv/xlsx/parquet always return file attachments with the full dataset (size-guarded at MAX_DOWNLOAD_SIZE_BYTES). ?format=json also returns the full dataset as a JSON file; without ?format=json, JSON …

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYes
datasetYes
formatNoOutput format: json, csv, tsv, xlsx, parquet
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, the description successfully discloses key behaviors: public access, pagination (limit, offset, cursor), format selection priority, file attachment downloads with size guard, and response format options. It could be improved by noting error handling or rate limits, but overall is fairly transparent.

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

Conciseness3/5

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

The description is front-loaded with the main purpose but becomes verbose. The trailing ellipsis indicates incompleteness, and some details (like format enumeration) could be more concise. It is adequate but not optimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 18 parameters and no output schema, the description covers core behaviors but leaves some gaps: the truncated ending suggests missing content, and it does not describe typical response structure beyond format. It is reasonably complete for a complex tool but not fully satisfactory.

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 78%, so baseline is 3. The description adds minimal parameter-specific insight beyond the schema (e.g., format selection priority and download behavior). It does not significantly enhance understanding of each parameter.

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 tool retrieves dataset data or subdataset list for a given provider/dataset. It specifically mentions flat vs hierarchical datasets and notes that metadata is available via a separate endpoint, distinguishing it from sibling tools like get_dataset_meta.

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?

It explains when to use this tool for data retrieval and mentions an alternative for metadata. However, it does not explicitly state when not to use it or provide clear exclusion criteria compared to other data query tools (e.g., sql_query or cross_dataset_query).

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