Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

hmt_trending

CJ Dropshipping /ad-trends (CJ Intelligence) viral ad creatives: name, category, platform (TikTok/Facebook), ad_age_days, views, likes, comp_price, cj_pid, sku, harvested_at — $0.03 per call Origin: https://hms-trending.ares-hms.workers.dev. Price: $0.03 per call via x402 (USDC on Base).

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": "hmt_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows returned (default 25, max 50)
categoryNoCategory fragment, e.g. "Home" (matches "Home & Garden")
platformNoAd platform filter, e.g. TikTok or Facebook
min_viewsNoMinimum creative views, e.g. 1000000
x402_paymentNoOptional. X-PAYMENT header value an x402 client produced after settling this exact origin+params challenge. Omit to first receive the Payment Required challenge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the commercially critical traits: a metered cost of $0.03 per call, x402/USDC-on-Base payment, and the serving origin. It does not state that this is a read-only operation, whether the paid response is cached, or how freshness works beyond the harvested_at field, leaving real gaps.

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

Conciseness3/5

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

The field list is efficient and front-loaded, but the pricing is stated twice ('$0.03 per call' appears in both the leading clause and the trailing 'Price:' sentence), and 'Origin: https://...' is glued onto the price sentence with no separator, making the structure read as machine-concatenated rather than authored.

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?

The field enumeration substitutes reasonably well for the absent output schema, and the payment mechanics are covered. However, with five parameters and a hard limit cap (default 25, max 50) and no offset parameter, the description says nothing about how to page past 50 rows, nor about data-freshness cadence, which an agent needs to plan calls correctly.

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 the baseline is 3; each parameter already carries its own description including the x402_payment handshake. The description reinforces the platform values (TikTok/Facebook) but adds no semantics for limit, min_views, or category beyond what the schema states.

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?

The description names the concrete upstream endpoint (CJ Dropshipping /ad-trends, CJ Intelligence), the resource type (viral ad creatives), and enumerates the returned fields (name, category, platform, ad_age_days, views, likes, comp_price, cj_pid, sku, harvested_at), so an agent knows exactly what it gets. It stops short of an explicit verb ('returns/lists') and does not differentiate itself from the sibling hmt_trending_batch, so a 5 is not warranted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus hmt_trending_batch, nor any prerequisite/context guidance. The only implicit signals are the filter parameters in the schema (category, platform, min_views), which the description does not frame as usage guidance.

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.