Skip to main content
Glama

Find datasets

find_datasets
Read-onlyIdempotent

Find open scientific datasets (and optionally models) that fit a research question, check their licences, verify the source papers (DOI, retractions, corrections), and return a citable Research Data Brief with a link that displays it as a page. The brief travels inside the link itself, so nothing is saved or published by this call. Searches DataCite (Zenodo, Figshare, Dryad and other data repositories), the Hugging Face Hub boosted by the Hugging Science curated index, and, for life-science questions, NCBI GEO, CZ CELLxGENE Discover (curated single-cell data) and the CZ CryoET Data Portal (cryo-electron tomography). Each result has a match level, a plain-language licence verdict, the source paper and whether it checks out, a citation for the data, and a line of code to load it. Every identifier comes from the repositories' own metadata; nothing is generated. The why field lists the facts behind the match: explain the fit to the user in your own words from those facts, and say plainly when the brief is empty. Pass keywords with English search words when the question is long or not in English. Licence verdicts come from repository metadata and are not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "find_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoField of the question. Life-science domains also search NCBI GEO.
keywordsNoEnglish search keywords (e.g. "triple negative breast cancer RNA-seq"). Recommended.
questionYesThe research question in natural language (e.g. "gene expression in triple-negative breast cancer").
max_resultsNoNumber of results, 1–5.
intended_useNoWhat the data is for. `commercial` demotes anything its licence does not clear for commercial use.publication
citation_styleNoStyle for the ready-made citations.apa
include_modelsNoAlso look for pretrained models on Hugging Face.

Output Schema

NameRequiredDescriptionDefault
quotaYes
statsYes
titleYes
resultsYes
questionYes
warningsYes
share_urlNo
takeawaysYes
suggestionsYes
intended_useYes
search_termsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / quota / properties / hint
      Added value: +{
      +  "enum": [
      +    "low",
      +    "intro"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / quota / properties / upgrade
      Added value: +{
      +  "type": "string"
      +}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses non-obvious behavior: the brief is embedded in the returned link so nothing is saved or published, identifiers come from repository metadata and are never generated, and licence verdicts are metadata-derived and not legal advice. These are exactly the caveats an agent needs to relay results responsibly.

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?

Purpose and the no-persistence guarantee are front-loaded, and every sentence carries information about sources, output anatomy, or caveats. However, it is presented as one dense paragraph with the result-field enumeration and the `why` instruction running together, which makes it harder to scan than a lightly structured version.

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 high-complexity, multi-source retrieval tool this covers sourcing, output anatomy, side effects, and disclaimer scope, and an output schema exists so return values need not be spelled out. The only omission is routing guidance relative to sibling retrieval tools, which leaves the agent to infer when this is the right call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the intent behind `keywords` (use English search words for long/non-English questions) and by describing the per-result `why` facts that the agent should paraphrase. The `intended_use` commercial-demotion note largely restates the schema, so it is not a full 5.

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?

States a specific verb and resource (find open scientific datasets, optionally models) and enumerates the exact sources searched (DataCite/Zenodo, Figshare, Dryad, HF Hub, Hugging Science, GEO, CELLxGENE, CryoET). This clearly separates it from siblings like search_papers and find_evidence, which retrieve literature rather than citable datasets.

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?

Gives concrete conditional guidance: pass `keywords` when the question is long or not in English, and life-science domains additionally trigger NCBI GEO. It also explains how to use the returned `why` field with the user. It never names an alternative tool or states when NOT to use this one versus find_evidence/search_papers, so 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.