Skip to main content
Glama

Loyal Spark Holder

Bazaar Probe x402

bazaar_probe_x402
Read-onlyIdempotent

Probe an x402 resource URL for its payment requirements without paying. Non-402 answers return an error, never the body. Read-only. No API key needed: keyless calls are limited to 20/minute per IP; with a key the key's own limits apply.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps endpoint to probe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotency and open-world access, yet the description adds real operational detail: non-402 responses yield an error rather than a body, and keyless calls are capped at 20/minute per IP while keyed calls inherit the key's limits. These are behaviors an agent could not derive from the structured fields and directly affect calling strategy.

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?

Four short sentences with no filler, and the core purpose along with its key qualifier is front-loaded. The rate-limit and error notes follow logically; nothing is redundant, though the sentences read as a slightly compressed list rather than fully structured prose.

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 single-parameter read operation with no output schema, the description covers purpose, failure behavior, authentication expectations and throughput limits. An agent has everything needed to decide whether and how to invoke it correctly.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents that it expects an HTTPS endpoint. The description adds no syntax, format, or validation nuance beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("Probe an x402 resource URL for its payment requirements") plus the critical scope qualifier "without paying," which distinguishes it from a pay-and-call capability. An agent can identify the operation and its pre-flight nature 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 phrase "without paying" and the error contract for non-402 answers make the intended use case (checking payment requirements before committing to a paid call) clear. It stops short of explicitly naming a sibling such as bazaar_pay_and_call as the follow-up alternative, so a 4 rather than a 5.

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