Skip to main content
Glama

Arbiter x402 Market Intel

Free preview of the x402 market map

market_peek
Read-onlyIdempotent

FREE. Snapshot time, catalog size, how many listings had a paying wallet in 30 days, and the category list, before paying for market_map or route_task.

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": "market_peek"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the one thing annotations cannot: 'FREE', i.e. zero cost, which is the decisive behavioral fact for a tool sitting in front of paid siblings. Rate limits or freshness guarantees for the free tier are not disclosed.

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

Conciseness5/5

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

One sentence, front-loaded with the single most important token ('FREE'). Every clause maps to a returned field or the sibling routing hint; nothing is redundant. The telegraphic list style is appropriate for a zero-argument preview tool.

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 input schema, no output schema and no parameter complexity, the description must carry the return-value burden, and it does by enumerating the four fields exposed. It stops short of clarifying caveats that matter for a free tier, such as caching, freshness, or whether the 30-day wallet count is exact or approximate.

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 the baseline is 4; there is no parameter meaning for the description to add or omit. The description correctly spends its words on return content instead of parameters.

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 enumerates exactly what the tool returns: snapshot time, catalog size, count of listings with a paying wallet in 30 days, and category list. It distinguishes itself from siblings by naming market_map and route_task and framing itself as the free preview step. It lacks an explicit verb ('returns'/'peek at'), but the content list makes the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before paying for market_map or route_task' gives clear ordering guidance: call this first, commit to paid tools only after. It does not state explicit exclusions (e.g. 'do not use this if you need full listing detail'), but the free-preview framing makes the boundary inferable.

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