Skip to main content
Glama
Sign In

akari-x402

by io.github.edvyno
OverviewDiscussionsAdmin

akari_catalog_report

x402 catalog report — the only graded census of the CDP Bazaar discovery index: every host we probed (791 as of 2026-11-09), how many answer a live 402 (462), the A-F grade for each with its defect ids, latency, and the defect distribution across the whole market. Built for directory operators, facilitators, and anyone deciding which sellers to court or which tooling to build. Delivered as JSON with per-host rows so it drops straight into a pitch list or a board report. Free

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses the return format (JSON with per-host rows), the data freshness date, the snapshot sizing, and that the call is free, which is notable for a paid-API context. It omits auth requirements, rate limits, and whether the snapshot updates between calls.

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?

Reasonably front-loaded: it states what the report is, gives the census numbers, then the audience and output format. Some marketing framing ("the only graded census") and a truncated trailing "Free " clause add minor noise, but the density is acceptable for the amount of information conveyed.

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 tool with no output schema, the description supplies the essential payload shape (per-host rows with grade, defect ids, latency, plus the market-wide defect distribution) and the freshness date. Missing details are secondary: payload size, refresh cadence, and whether historical snapshots are accessible here versus the history sibling.

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 score applies, and the description has nothing to clarify beyond confirming there is no configuration. No parameter meaning is lost.

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 ("graded census of the CDP Bazaar discovery index") and quantifies the scope (791 hosts probed, 462 returning a live 402) along with the A-F grading and defect metadata. This makes the deliverable unambiguous. It doesn't explicitly contrast with the sibling akari_catalog_report_history, though the "as of 2026-11-09" snapshot framing does hint at the distinction.

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?

The audience is named ("directory operators, facilitators, and anyone deciding which sellers to court or which tooling to build"), which implies when to reach for it. However, no explicit when-not conditions or alternative tools are named, including the obviously adjacent history sibling, so the agent must infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All akari-x402 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources