Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

audio_payment_status

Read-onlyIdempotent

Verify existing audio payment status through Quantum Financial using its original delivered response. This read-only lookup never starts separation or payment. Preserve the original payment identifier; if replay storage has expired, supply exact response_b64.

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": {
      "payment_identifier": "<payment_identifier>",
      "buyer_agent_id": "<buyer_agent_id>"
    },
    "name": "audio_payment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_b64No
buyer_agent_idYes
payment_identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 largely covered. The description adds useful behavioral context: the lookup never starts separation or payment, and the response_b64 fallback applies only when replay storage has expired. It does not mention authentication requirements or what status information is returned.

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?

The description is three tight sentences with the core purpose front-loaded. The scope boundary and fallback condition follow logically, and every sentence adds useful information without repetition.

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?

With no output schema and zero parameter descriptions, the description should ideally say more about the input and return contract. It covers the read-only behavior and two of the three parameters, but omits buyer_agent_id and does not describe what status fields the lookup returns.

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 compensate, and it provides meaningful constraints for two parameters: preserve the original payment_identifier and supply exact response_b64 only if replay storage has expired. However, the required buyer_agent_id parameter is left completely unexplained, leaving a third of the input contract undocumented.

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 gives a specific verb and resource: 'Verify existing audio payment status through Quantum Financial.' It further clarifies that this is a read-only lookup that 'never starts separation or payment,' which helps distinguish it from initiating tools, but it does not name a sibling alternative.

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

Usage Guidelines4/5

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

It clearly states the use case: checking an existing audio payment status using the original delivered response. It also provides an explicit exclusion ('never starts separation or payment') and a fallback condition for response_b64, though it does not name an alternative tool to use for related tasks.

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