Skip to main content
Glama

Bazaar Listing Guard

listing_guard
Read-only

Use when you need a detailed public listing metadata check. Bazaar Listing Guard: CDP technical validation plus a bounded heuristic metadata screen for agent-directed instructions, embedded URLs, tool calls, invisible Unicode, long fields and prices above 100x a fresh Scout category median. Returns riskScore, flagged spans and rewrite suggestions. Not Coinbase policy certification or guaranteed detection. Public HTTPS only; no target payment or request bodies stored. Price $0.05 USDC on Base; shared trial may apply. Price: 0.05 USDC. Minimal input example: {"url":"https://api.spendpreflight.com/v1/check","method":"GET"}. Illustrative output excerpt: {"cdpPreflight":{"valid":true,"preflight":[],"index":null},"riskScore":0,"flags":[],"suggestedRewrite":[],"screenComplete":true,"priceCompared":false,"indexActive":null,"example_note":"Illustrative response only; not a live result or safety guarantee."}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): First use the existing shared allowance of 3 eligible calls per IP per UTC day, without payment metadata. This is shared with eligible HTTP trials, not a new allowance. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

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>",
      "method": "<method>"
    },
    "name": "listing_guard"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Exact public resource URL string, including path; no credentials. Example: https://api.example.com/data.
methodYesRequired. Advertised HTTP method string, not a new target request. Example: GET. Supply when cached methods are ambiguous.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / method / description
      Added value: +"Required. Advertised HTTP method string, not a new target request. Example: GET. Supply when cached methods are ambiguous."
    • addedInput schema / properties / url / description
      Added value: +"Required. Exact public resource URL string, including path; no credentials. Example: https://api.example.com/data."
  2. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: public HTTPS only, no target payment or request body storage, bounded heuristic screening, no guaranteed detection, no Coinbase policy certification, trial limits, and payment handling constraints. These details materially help an agent understand side effects, limits, and safety posture. The readOnlyHint/openWorldHint annotations are consistent with the described read-only public-resource screening.

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

Conciseness2/5

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

The purpose is front-loaded, but the description is heavily bloated with repeated price information, lengthy x402 payment procedures, duplicate illustrative output excerpts, and multiple disclaimer sentences. Much of this is not needed to select or invoke the tool and obscures the core screening behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description supplies the needed return concepts and an illustrative output excerpt, along with storage, safety, and payment prerequisites. It is complete enough for an agent to understand what the tool returns and the constraints around calling it, even though it is overlong.

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 description coverage is 100%, so the schema already documents both url and method, including constraints and examples. The description reinforces that access is public HTTPS only and that method is advertised rather than a new target request, but this largely duplicates the schema wording. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 gives a specific purpose: CDP validation plus heuristic screening for listing metadata risks such as embedded URLs, tool calls, invisible Unicode, long fields, and outlier prices. It also names return fields (riskScore, flagged spans, rewrite suggestions). However, it does not distinguish this from likely siblings such as check_listing or security_check.

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 provides a trigger condition: 'Use when you need a detailed public listing metadata check.' That gives implied usage but no explicit when-not guidance and no named alternatives among the many sibling check tools. The extensive payment instructions are procedural, not usage selection 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.