Skip to main content
Glama

Find open datasets

find_open_datasets

Find open research datasets you may use, each with a plain licence verdict (public domain, attribution, share-alike, no-derivatives, non-commercial, not stated) read from Zenodo's structured licence, plus DOI, authors and file links. Default: only commercially usable ones. A search with nothing usable is refused before payment. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "q": "<q>"
    },
    "name": "find_open_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYeswhat data you need, in plain words
sizeNodatasets to return, 1-20 (default 10)
sortNobestmatch (default) or mostrecent
licenceNocommercial (default) or any
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the $0.004 x402 cost, accepted chains/tokens, the two-step terms-then-payment handshake, and that empty results are refused before payment. Unstated are failure/retry semantics for an invalid payment payload, which keeps it off a 5.

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?

Front-loaded with the value proposition in the first sentence, then defaults, then pricing and payment steps. Dense but every sentence carries information; the long first sentence is slightly overloaded with parenthetical licence categories.

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?

With no output schema, the description adequately sketches the return shape (licence verdict, DOI, authors, file links) and fully covers the payment gating that would otherwise surprise an agent. Only the error/response detail for a rejected payment is missing.

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 goes beyond the schema by explaining the workflow for the `payment` parameter (call without it to get terms, sign with your own wallet, call again with the signed payload) and by restating the default for the licence filter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 research datasets') plus the distinctive output: a plain licence verdict derived from Zenodo's structured licence, DOI, authors and file links. That is far more than a restatement of the name. It does not name a sibling alternative such as dataset_finder or research_search, so it stops short of 5.

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?

Gives useful context: default is 'only commercially usable ones', a search with nothing usable is refused, and call-once-then-call-again payment flow. But there is no explicit when-not guidance or comparison against the many sibling search/data tools, leaving the agent to infer selection.

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.

Resources