Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

bazaar_nft_gates

Read-onlyIdempotent

Free, zero-auth NFT holder discount & entitlement tier breakdown for Bazaar skills.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that by stating the call is free and requires zero auth, which affects how an agent should plan around it. It says nothing about the shape or size of the returned tier breakdown, which is the main remaining behavioral gap.

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 fragment with no padding, which is appropriate for a trivially invoked tool. It is slightly compressed to the point of jargon ('Bazaar skills'), but nothing in it is wasted.

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-only lookup the description covers what the tool is and its auth/cost profile. With no output schema, however, an agent has no idea what a 'tier breakdown' contains, for example whether it is a static tier table or holder-specific entitlements, and that ambiguity is not resolved.

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 and the schema is empty with additionalProperties false, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies no inputs are needed by advertising it as zero-auth.

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 resource: an NFT holder discount and entitlement tier breakdown for Bazaar skills. It is clear what the tool returns, though it is a noun phrase rather than a verb+resource statement and it never distinguishes itself from the closely named sibling bazaar_pricing_tiers.

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?

There is no when-to-use or when-not-to-use guidance. Siblings bazaar_pricing_tiers, bazaar_quote, and bazaar_catalog plausibly overlap, yet the description gives no condition for choosing this tool over them. The only usage signal, 'free, zero-auth', describes cost and auth, not selection criteria.

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