HuggingFace Trending Models (hftrendingwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: HuggingFace Trending Models (hftrendingwatch). Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the top trending HuggingFace models right now?; Show me trending text-to-image models.. 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 11, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful behavior — no API key required and a 20-queries-per-session cap — but the '0.01 USDC/query' pricing statement sits in tension with 'no payment', which could confuse an agent about cost.

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 lead is marketing ('✅ No API key needed') rather than the tool's function, and the no-key/no-payment point is repeated three times across the text. Sample questions and price lines crowd out the actual behavioral description, so several sentences do not earn their place.

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 simple, zero-required-parameter, read-only tool with full schema coverage and annotations, the essentials are present. What is missing is the relationship to the sibling paid-query tools and a clear statement that the preview returns only public metadata, which the schema mentions but the description does not.

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 coverage is 100%, with both 'slug' and 'question' fully described in the schema itself. The sample questions loosely illustrate the 'question' field and the 'echoed back' nature is only in the schema, so the description adds essentially nothing beyond structured fields — baseline 3.

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?

The description does name the underlying listing (HuggingFace Trending Models / hftrendingwatch) and calls itself a 'FREE preview', so an agent can infer this returns a taste of listing data. But it never states what the tool actually returns or how the preview differs from a real query, and the 'Price 0.01 USDC/query' line muddies whether this is free or paid.

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?

Usage is only implied: 'FREE preview — no key, no payment' suggests trying before paying, and sample questions show intended inputs. It never names the paid alternative (data_session_query / data_session_open) or states the condition that should push the agent to the real tool instead of the preview.

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

All HuggingFace Trending Models (hftrendingwatch) 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?