HuggingFace New Dataset Release Tracker (hfdatasets)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: HuggingFace New Dataset Release Tracker (hfdatasets). Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the newest HuggingFace datasets released today?; Show me recent datasets tagged text-classification.. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint and no auth, but the description adds concrete operational context: no API key required and a rate ceiling of max 20 queries/session. The 0.01 USDC/query figure is listing pricing rather than this tool's cost, which is slightly muddling, but the auth and rate-limit disclosures are real value beyond the annotations.

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

Conciseness2/5

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

The description leads with a checkmark emoji rather than the tool's function and repeats the same point twice ("No API key needed" and "no key, no payment"). Price, sample questions, and a call to action crowd out the actual definition, so the text is promotional padding rather than front-loaded substance.

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?

For a two-parameter read-only tool with no output schema, the description should say what a preview actually returns — the schema note ("public metadata only") covers this, but the description does not. The auth and rate-limit facts are present, yet the crucial behavior that the free-text question is echoed rather than answered appears only in the schema.

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 100%, so both slug and question are already documented, including the key caveat that the question is "echoed back." The sample questions in the description do illustrate the expected shape of the question argument, but they are illustrative marketing text rather than added syntax or constraint information.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"FREE preview — no key, no payment" plus the listing name signal that this returns a free sample of a specific paid dataset listing, but the description never states the verb+resource outright (it never says it returns listing metadata or a preview of the data). The opening line is promotional rather than a definition, so an agent must infer the purpose from the pricing and sample-question framing.

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?

Two sample questions ("What are the newest HuggingFace datasets released today?") imply how to use the tool, and "Try one of the sample questions now" nudges usage. However, no sibling is named as an alternative — notably data_session_query, the paid query path — and there is no when-not guidance (e.g. that the preview only returns public metadata and the question is not actually answered).

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

All HuggingFace New Dataset Release Tracker (hfdatasets) 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.

Resources

Need Help?