Skip to main content
Glama

HMS x402 Data Origins (RE Data Refinery + Storefront)

sf_gta6_outliers

GTA6 money content outlier scan — scored YouTube outliers ranked by viral potential (title, source URL, views, channel, duration, score, suggested angle) — $0.03 per call Origin: https://storefront-data-hms.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": "sf_gta6_outliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior3/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. It does disclose the pricing model ($0.03 per call via x402, USDC on Base) and the payment-challenge flow, which is genuinely useful behavioral context. However, it says nothing about data freshness, result limits, or whether the scan is read-only and side-effect free beyond the payment.

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 core purpose and return fields are front-loaded, which is good, but pricing is stated twice in the same sentence (once inline and once as 'Price: $0.03 per call via x402'), and the origin URL is wedged into the middle of the description. Some tightening would improve it.

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 compensates by enumerating the returned fields, and it explains the payment prerequisite, which is the main risk of calling it wrong. What is missing is any statement of scope or result volume — the tool accepts no filtering parameters, so the description should say what the scan actually covers.

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% and the single parameter's purpose is fully documented in the schema itself, so the baseline is 3. The description adds cost and settlement details (price per call, USDC on Base) that give meaning to why the x402_payment parameter exists, pushing it above baseline.

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 uses a specific verb and resource — a scan that returns scored YouTube outliers ranked by viral potential — and enumerates the returned fields (title, source URL, views, channel, duration, score, suggested angle). It is clear what the tool does, though it never names or distinguishes itself from any sibling tool.

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 explicit when-to-use guidance and no mention of alternatives or exclusions, despite nearby tools such as hmt_trending that could plausibly overlap. An agent can infer the use case from the purpose statement but receives no routing help.

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.