Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

bazaar_quote

Read-onlyIdempotent

Free, zero-auth price quote for any Agent Bazaar skill with optional holder wallet discount preview.

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": {
      "skill_id": "<skill_id>"
    },
    "name": "bazaar_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNo
skill_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive) and openness, but the description adds genuinely new operational facts: the call is free, requires no authentication, and the wallet input only previews a holder discount rather than committing to a purchase. Rate limits and error behavior remain undisclosed, keeping it below a 5.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the most decision-relevant facts (free, zero-auth, quote, optional discount) all appear immediately.

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 two-parameter, read-only quoting tool with no output schema, the description covers cost, auth, scope, and the optional discount path adequately. Only the shape of the returned quote is left unspecified, which is a minor gap for a simple 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 description coverage is 0%, so the description must carry the burden; it clarifies that 'skill' maps to the skill_id parameter and that wallet is an optional discount-preview input. It does not explain the address format or the consequences of supplying a non-holder wallet, leaving half the semantics to the raw schema.

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 names a specific verb and resource: 'price quote for any Agent Bazaar skill,' so an agent knows this is a read-only pricing lookup scoped to Bazaar skills. It does not explicitly differentiate itself from sibling quote tools like payment_assistant_quote or bazaar_pricing_tiers, so it falls short of a 5.

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 supplies useful qualifying context ('free, zero-auth,' 'optional holder wallet discount preview') that implies when the tool is appropriate, but never states when to prefer it over the sibling quote or pricing-tier tools. Usage is implied rather than prescribed.

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