Skip to main content
Glama
Sign In
x402 Endpoint Scanner

x402 Endpoint Scanner

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

x402 Bazaar health census stats

census_stats
Read-onlyIdempotent

Fetches live ForgeMesh catalog stats alongside static August 2026 x402 Bazaar census figures, so you can benchmark seller health, dead endpoints, free content leaks, and MPP adoption.

Instructions

Fetches the latest ForgeMesh catalog stats (best-effort, 5s timeout, no input required) alongside the static headline numbers from the August 2026 x402 Bazaar health census: 1,225 sellers probed, 74% healthy, 206 dead, 40 serving paid content for free, and 15% MPP dual-stack. Source: https://forgemesh.io/blog/x402-bazaar-health-census-august-2026

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, but the description adds two things they cannot: the call is best-effort with a 5s timeout, and the census figures are static August 2026 numbers rather than live data. Disclosing that half the payload is frozen snapshot data is exactly the kind of caveat that prevents an agent from misreading stale values as current.

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 front-loaded sentence: verb and resource first, then the timeout caveat, then the enumerated figures. The inline metric list is somewhat dense but it is the actual content of the snapshot, and the trailing source URL is short and useful provenance.

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-argument tool with full annotation coverage and no output schema, the description covers what is fetched, that it is best-effort, and what the headline numbers are. It does not say what an agent should expect to receive when the 5s timeout fires (error versus partial payload), which is the one residual gap.

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?

There are zero parameters, so the baseline is 4; the description confirms 'no input required' and matches the empty schema. Nothing further is needed on this dimension.

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 opens with a specific verb and resource: 'Fetches the latest ForgeMesh catalog stats' alongside static census headline numbers. That is clearly distinct from scan_batch/scan_endpoint, which imply active scanning rather than a stats snapshot, though the description never names those siblings to make the contrast explicit.

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?

Usage context is only implied: 'no input required' and 'best-effort, 5s timeout' tell an agent this is a cheap zero-argument snapshot that may fail. There is no explicit statement of when to prefer this over scan_batch (e.g. 'use for a quick overview before running scans') and no when-not guidance.

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

Deploy Server

Other Tools