Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

collab_access_check

Read-onlyIdempotent

Founders and Sound System Key holder tier status check on Base Unpaid calls return HTTP 402 requirements; retry with payment_signature.

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": {
      "wallet": "<wallet>"
    },
    "name": "collab_access_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes
order_refNo
credit_keyNo
wallet_proofNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds genuine value beyond them by disclosing the x402-style payment gate: unpaid calls return HTTP 402 and must be retried with payment_signature. It still omits what a successful response contains and what authorization the other credential-like params represent.

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

Conciseness3/5

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

It is a single compact sentence with no filler, and the payment caveat is placed second where it belongs. But the front-loaded clause is dense and hard to parse, and a semicolon splice joins two unrelated ideas without clear structure.

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 a tool with 6 parameters, 0% schema coverage, and no output schema, the description is far too thin: five parameters have no meaning anywhere, and the meaning of 'tier status' results is left to inference. Only the 402/payment_signature flow is adequately covered.

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% across 6 parameters, so the description carries the burden. It explains the role of only payment_signature (the 402 retry credential) and leaves the required wallet, credit_key, wallet_proof, wallet_address, and order_ref entirely undefined.

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 conveys that this checks tier/key-holder access status ('Founders and Sound System Key holder tier status check on Base'), which is more specific than the bare name. However, the phrasing is compressed and grammatically tangled, and it never states plainly that it returns an access/tier result for a wallet.

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 implicitly indicates usage (check whether an address holds Founder or Sound System Key holder tier status), but gives no explicit when-to-use framing and names no alternative among the many sibling tools (e.g. bazaar_pricing_tiers, payment_assistant_*). The retry advice describes an error path, not tool selection.

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