gdex-mcp

get_dataset_files

Return a paginated file listing for a dataset or a specific group.

Depending on how deep gindex is in the group hierarchy, this returns
either actual file rows or another layer of subgroup summaries — there's
no way to tell in advance which you'll get. If you get subgroups, read
the gindex (or url) off a row and call again with that gindex to go one
level deeper; gindex values are dataset-specific and can't be guessed.

A shallow gindex on a large dataset can return a very large response
(thousands of files) — the file-row portion of the response is capped at
500 rows (look for "_truncated": true). Two ways to avoid hitting that
cap instead of drilling down group by group: pass filter_wfile with a
filename pattern (e.g. a date like "20220808") to filter down to matching
files, or page through a known group's results with `page`. filter_wfile
only filters actual file rows, so it has no effect at a gindex that's
still returning a subgroup summary rather than files — if a first attempt
comes back unfiltered, descend one level (see get_file_groups) and retry
there.

Args:
    dsid: Dataset ID (dNNNNNN), e.g. d083002
    gindex: Optional group index to filter files
    page: Page number to fetch (for a group with more files than fit on one page)
    filter_wfile: Filter files by name pattern, e.g. "20220808" to match a date
    fl: File list source (defaults to "web" server-side)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fl`	No
`dsid`	Yes
`page`	No
`gindex`	No
`filter_wfile`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it excels: it details pagination, the 500-row cap with '_truncated': true, the gindex being dataset-specific and unguessable, and the fact that filter_wfile only affects file rows and not subgroup summaries. These are critical behaviors an agent must know to avoid failed calls.

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?

Though lengthy, every sentence earns its place. The key caveat (subgroup vs file rows) is front-loaded, followed by concrete avoidance strategies, then a clean Args section. The structure is logical and free of redundancy.

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, no annotations, no output schema shown but present), the description covers all necessary aspects: pagination, truncation, filtering behavior, gindex navigation, and parameter defaults. Since an output schema exists, not describing the return format in detail is acceptable. Nothing an agent needs to invoke correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by listing each parameter (dsid, gindex, page, filter_wfile, fl) with concrete explanations, including examples like 'd083002' for dsid and the date pattern '20220808' for filter_wfile. This adds meaning far beyond the bare schema types.

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 opens with 'Return a paginated file listing for a dataset or a specific group', which clearly specifies the action (return), the resource (file listing), and the scope (dataset or group). It also distinguishes itself from siblings like get_file_groups by explicitly referencing that tool for descending one level, making differentiation obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: it explains the unpredictable subgroup-vs-file response, advises calling again with a gindex to go deeper, and offers two strategies (filter_wfile or page) to avoid truncation. It also points to get_file_groups as the alternative when descending a level, giving clear routing instructions.

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

All gdex-mcp 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.