Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

bazaar_pricing_tiers

Read-onlyIdempotent

Free, zero-auth Agent Bazaar pricing tier table.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bazaar_pricing_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one piece of genuinely new context – no authentication or cost is required – but says nothing about what the returned table contains (tiers, fields, units) despite there being no output schema.

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 compact sentence with the distinguishing traits ('free, zero-auth') placed first. Nothing is wasted, though the brevity borders on under-specification rather than efficiency.

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

Completeness3/5

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

For a zero-parameter read tool this is nearly adequate, but with no output schema the description should at least sketch what the tier table returns (tier names, thresholds, pricing units). As written, an agent knows it is a free unauthenticated lookup but not what it will get back.

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

Parameters4/5

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

The tool takes zero parameters, so the schema carries no semantics to supplement; baseline 4 applies. The description correctly implies the call is parameter-free by describing a static table.

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

Purpose3/5

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

The description names a specific resource ('Agent Bazaar pricing tier table') and signals it is a lookup, but there is no verb (get/list) and nothing distinguishes it from nearby siblings such as bazaar_quote or bazaar_catalog, which plausibly also return pricing information. An agent can guess this returns a static tier table but cannot confirm how it differs from a quote call.

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 call this versus bazaar_quote (which presumably returns a computed price) or bazaar_catalog. 'Free, zero-auth' hints that it is a safe, always-available call, but there are no explicit use conditions or exclusions.

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