Skip to main content
Glama

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

x402-market-lite

[x402 paid: $0.005 USDC on Base] x402 Market Lite: the $0.005 slice of the market snapshot - price distribution (median $0.009, p90 $0.05), network split, top tags, methods and the 10 most expensive endpoints. Same raw data as the $0.10 report, priced for everyday agent use. 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-lite"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 non-obvious trait: tools/call returns a live payment challenge and each call costs $0.005 USDC on Base. It does not explain what happens after payment, whether an unpaid call errors or returns the challenge in-band, or retry semantics — gaps a paywalled tool should cover.

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?

A single dense sentence plus one short sentence, with the price tag and contents front-loaded so an agent can triage cost and scope quickly. Some promotional filler ("priced for everyday agent use," "the $0.005 slice") could be cut without losing meaning.

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?

For a zero-parameter, no-output-schema tool, the definition covers price, content, and payment-challenge behavior, which is most of what an agent needs. It stops short of describing the payment/challenge mechanics or what a successful response contains, which matters given no annotations and no output schema to fall back on.

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 schema semantics to add and the baseline of 4 applies. The description correctly implies a fixed, argument-free request rather than hinting at unseen inputs.

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 contents returned (price distribution with median/p90, network split, top tags, methods, 10 most expensive endpoints) and frames itself as the $0.005 tier of a larger report, so the resource is unmistakable. It lacks a clean verb and leans on marketing phrasing ("priced for everyday agent use"), but the scope distinction from the $0.10 report is 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?

It implies selection guidance by positioning itself as the cheap slice versus "the $0.10 report," which lets an agent infer a cheaper-vs-fuller tradeoff. However, it never explicitly says when to prefer this over x402-market-report or what the paid call flow requires before invoking, leaving the choice implied rather than stated.

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