Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

hmt_trending_batch

FULL export of the CJ /ad-trends viral ad-creative harvest (all rows, limit max 1000) — $0.50 per call Origin: https://hms-trending.ares-hms.workers.dev. Price: $0.50 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_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows returned (default all, max 1000)
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

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose real behavioral traits: a per-call cost of $0.50, x402 payment settlement in USDC on Base, the origin host, and the 1000-row ceiling. It does not describe what a row contains or how large the export typically is, which is the main remaining gap for a paid bulk endpoint.

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 purpose and row limit are front-loaded, which is good, but the price is stated twice in the same sentence ('$0.50 per call' and 'Price: $0.50 per call via x402'), and the bare origin URL sits awkwardly mid-sentence. Trimming the duplicate price would tighten it without losing information.

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?

Cost, payment mechanics, origin, and row cap are all covered, which is the important part for a paid tool. However, there is no output schema and the description never characterizes the returned records (fields, freshness, deduplication), so an agent cannot judge what the export actually yields.

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%, and both parameters (limit and x402_payment) are fully documented in the schema including the challenge/settlement flow. The description only restates the limit ceiling, adding no meaning beyond the schema, so the baseline of 3 applies.

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 states a specific action and resource: a 'FULL export of the CJ /ad-trends viral ad-creative harvest' returning all rows. The word 'FULL' plus 'all rows, limit max 1000' implicitly contrasts with the sibling hmt_trending, but that sibling is never named, so differentiation is inferred rather than stated.

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: an agent can guess this is the complete-dump variant versus a lighter sibling, but the description never says when to choose this over hmt_trending or what conditions make the $0.50 full export worthwhile. No explicit exclusions or alternatives are given.

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.