Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_decide_approval

Approve or deny a pending single-use subagent spend approval ticket (sba_*) using the master Stripe account key.

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": {
      "approval_id": "<approval_id>",
      "decision": "<decision>"
    },
    "name": "payment_assistant_decide_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
decisionYes
spend_keyNo
credit_keyNo
approval_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnly=false, destructive=false, idempotent=false, openWorld=true, and the description adds two pieces of real context beyond that: the operation is gated on a 'master Stripe account key' and the ticket is single-use. It does not explain the consequences of the non-idempotent flag (e.g. whether a retry on a consumed ticket errors), whether deny is terminal, or whether funds move on approve.

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 with the action first and the qualifying scope second; no filler. It is arguably too terse for a five-parameter mutation tool, 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 write tool with no output schema and 0% schema coverage across five parameters, the description leaves meaningful gaps about the key parameters and the post-decision state. It does at least establish the authentication mechanism and the ticket domain, but an agent could not confidently populate spend_key versus credit_key from this text alone.

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

Parameters2/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 only implicitly covers approval_id (via the sba_* mention) and decision (approve/deny); spend_key, credit_key and note are left entirely unexplained, and 'master Stripe account key' is ambiguous about which of the two key parameters it refers to.

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?

States a specific verb pair (approve or deny) against a specific resource (a pending single-use subagent spend approval ticket) and even pins the ID format (sba_*). That is enough to separate it from the request/creation side of the flow, though it never names payment_assistant_request_approval as the counterpart.

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?

Usage is only implied: the ticket must already be 'pending', which tells the agent this is the resolution step rather than the request step. There is no explicit when-not guidance, no statement about what happens to an already-decided ticket, and no pointer to the sibling that creates tickets.

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