Skip to main content
Glama

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

x402-market-report

[x402 paid: $0.100 USDC on Base] x402 Market Snapshot: live stats over the FULL PayAI discovery feed (16,229 services, 1,588 hosts) - price distribution (min/median/p90/max), network split (Base/Solana), AI vs data APIs, freshness, top-10 most expensive endpoints. 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-market-report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does disclose key traits: it costs $0.100 USDC on Base and invoking tools/call returns a live payment challenge rather than the report itself. It does not describe rate limits, caching, or the exact response shape after payment, so it stops short of full transparency.

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

Conciseness4/5

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

The definition is a single dense sentence that front-loads the payment cost followed by the report scope and contents. It is efficient with no filler, though the run-on list of metrics is slightly harder to parse than a structured breakdown would be.

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?

For a zero-parameter paid report with no output schema or annotations, the description is largely complete: it states the cost, chain, token, data source, metrics included, and the payment-challenge behavior. It could be more complete by explaining how to satisfy the challenge after the 402 response and what the successful payload looks like.

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 tool takes zero parameters, so there is no parameter meaning for the description to add. The schema is empty and the description correctly focuses on output content and payment behavior instead.

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 specific resource (PayAI discovery feed snapshot) and enumerates the exact metrics returned: price distribution, network split, AI vs data APIs, freshness, and top-10 expensive endpoints. It also emphasizes 'FULL' feed versus an implied 'lite' sibling, but it never explicitly names or contrasts a sibling tool, which keeps it just short of a 5.

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 or when-not-to-use guidance. The 'FULL' qualifier hints that a lite alternative exists, but the definition never tells the agent to choose this tool over x402-market-lite or x402-demand-report, nor does it state prerequisites beyond the payment note.

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