Skip to main content
Glama

Loyal Spark Holder

Bazaar Pay And Call

bazaar_pay_and_call

Pay an x402-protected endpoint with USDC on Base and return its response.

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_pay_and_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps x402 endpoint
bodyNoOptional JSON body
methodNoHTTP method (default GET)
max_usdcNoSpend cap in USDC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds the payment rail (USDC on Base) and that the endpoint's response is returned, but omits the critical consequence of non-idempotency: a retry spends again, and it says nothing about failure handling, spend-cap enforcement, or irreversibility of the transfer.

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 naming the action, asset, network, and return behavior with zero filler. Its brevity is efficient, though it comes at the cost of missing guidance rather than being bloated.

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

Completeness2/5

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

For an open-world, non-idempotent, payment-spending tool with a nested body parameter and no output schema, the description is thin: no mention of duplicate-payment risk, prerequisites, supported networks beyond Base, or what a caller should do when the endpoint returns an error.

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%, so all four parameters are documented in the schema; baseline 3 applies. The description only implies the currency/network context ('USDC on Base') and adds no detail on method, body, or how max_usdc is enforced.

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?

States a specific verb and resource: pay an x402-protected endpoint with USDC on Base and return its response. This is clearly distinguishable from discovery/probe siblings like bazaar_probe_x402, though it does not name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus bazaar_probe_x402 or the discover tools, no prerequisites (wallet? balance? supported networks?), and no exclusions. An agent knows what it does but not when it is the correct choice.

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