Skip to main content
Glama

Settle Watch

Why isn't my x402 endpoint in the Bazaar?

check_listing
Read-only

For sellers: check whether an x402 endpoint is listed in Coinbase's Bazaar and, if not, why. Runs Coinbase's public validator (the indexer's own checks), looks the payout address up in Coinbase's merchant list, and adds the Settle Watch's 30-day availability against Coinbase's 99% bar for featured listings. Returns findings with a fix for each.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full https:// URL of your paid endpoint
methodNoHTTP method of the route (default GET)

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 and openWorldHint, yet the description adds real substance: it discloses the three external checks performed (public validator, merchant-list lookup, Settle Watch 30-day availability against the 99% featured bar) and that output is 'findings with a fix for each'. It does not mention latency, rate limits, or what happens when the merchant lookup fails.

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?

Three tightly ordered sentences: purpose, method, return shape. It is front-loaded with audience and goal, and the parenthetical '(the indexer's own checks)' earns its place by clarifying validator provenance. Dense product jargon (Bazaar, Settle Watch) slightly limits readability but does not waste space.

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 only two parameters, no output schema, and annotations covering the safety profile, the description does what's needed: it explains the checks run and that results come back as findings with remediation. Missing only operational details such as runtime or prerequisites for the merchant lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both url and method documented in the schema, so the description needn't restate them. It introduces a 'payout address' concept used internally but never explains where that value comes from relative to the two declared parameters, leaving a small ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('check whether an x402 endpoint is listed in Coinbase's Bazaar') plus a diagnostic extension ('and, if not, why'), and scopes the audience with 'For sellers'. An agent can distinguish this diagnostic listing check from a payment-status check without opening the schema.

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 'For sellers' framing and the 'why isn't it listed' question give a clear triggering context: an endpoint the seller believes should be listed. It does not state when-not to use it or name an alternative (e.g., the payment-check sibling), so it stops short of full routing guidance.

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.