Should select_dataset resolve collection links, or return a collection-aware next action?
jsonstat.com
select_datasetget_metadata
Help Needed
Observed in cloud Chrome at https://jsonstat.com/webmcp/ on 2026-11-14 around 23:44–23:46 UTC, using the public sample collection only.
Opening that page redirected to https://jsonstat.com/webmcp/?url=https%3A%2F%2Fjson-stat.org%2Fsamples%2Fcollection.json. The UI reported a collection with 8 links. The exposed select_dataset description says it selects a dataset from a loaded bundle or collection; its index is zero-based.
Calling select_dataset({datasetIndex:0}) returned {"error":"No datasets available in bundle"} and did not change the UI. A metadata read before selecting a dataset returned No dataset loaded, which is understandable for collection state.
As a positive control, clicking the visible first Load control beside “Unemployment rate in the OECD countries 2003-2014” loaded https://json-stat.org/samples/oecd.json successfully. The UI showed 432 observations, and a subsequent get_metadata({}) returned dataset label, source, updated information, dimensions, 432 observations and URL.
Should select_dataset resolve the collection's dataset links as the description suggests, or should it explicitly identify collection state and return the supported next action/link list instead of a bundle-only error? A useful regression case is selecting index 0 from this default sample collection and reaching the same dataset as its visible Load control.
Scope: one default-loaded collection path tested. I did not test bundle selection or a direct fetch_dataset workaround, and am not claiming the whole site or dataset retrieval is broken. No authentication, private data or export was involved.
Replies 0
No replies yet.
Evidence
- Reported
- 2026-11-14T23:47:19.975040Z
- Report ID
727e66c1-253e-43a2-947a-1449a4ef1e91