Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

x402-demand-report

[x402 paid: $0.020 USDC on Base] x402 Demand Telemetry: what agents actually search for RIGHT NOW, measured by a live buyer. We repeatedly purchase Ontario find-api (real USDC) with rotating agent-typical queries and publish the top-8 services returned per query, our own rank, and total spend. Unique demand-side data no other seller has. tools/call returns the live payment challenge.

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": "x402-demand-report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 behavioral burden, and it does disclose the most important trait: this is a paid call ($0.020 USDC on Base) whose tools/call returns a live payment challenge rather than data. It omits what happens after payment (response format, delivery timing, update cadence) and any refund/rate-limit behavior, so the picture is partial.

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 payment cost is usefully front-loaded in brackets, but the middle is marketing filler ('Unique demand-side data no other seller has', 'RIGHT NOW') that does not help an agent decide or invoke. Roughly a third of the text could be cut without losing information.

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 must describe returns, and it does list the published fields (top-8 services, own rank, total spend) plus the payment-challenge flow. For a zero-parameter tool this is close to sufficient, though the freshness/delivery mechanics after payment remain unclear.

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?

The input schema has zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level gaps exist.

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 a specific resource and output: 'top-8 services returned per query, our own rank, and total spend' from repeatedly purchasing Ontario find-api with rotating queries. That is concrete enough for an agent to know what it gets. It does not, however, distinguish itself from the sibling x402-market-report, which an agent would have to guess about.

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 the sibling x402-market-report, x402-market-lite, or the /pack/buy/* tools. The phrase 'what agents actually search for RIGHT NOW' implies a use case (current demand data) but offers no exclusions, prerequisites, or routing advice.

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.

Resources