Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_request_approval

Create a pending single-use human-in-the-loop spend escalation approval ticket (sba_*) when a delegated subagent needs one-time permission above its standing cap or route allowlist.

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": "payment_assistant_request_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNo
centsNo
routeNo
spend_keyNo
credit_keyNo
ttl_minutesNo
justificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, open-world and non-idempotent behavior, so the safety bar is lower. The description adds that the result is a pending, single-use ticket requiring human action and that IDs carry an sba_* prefix, but says nothing about duplicate-request risk (relevant given idempotentHint=false), expiry semantics, or how the requester learns of the decision.

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?

A single front-loaded sentence with no filler; every clause (pending, single-use, human-in-the-loop, sba_*) carries information.

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 7-parameter creation tool with no output schema, no annotations about approval latency, and 0% schema coverage, the description leaves critical calling details (which fields are needed, what ttl_minutes controls, what spend_key/credit_key scope) unaddressed. It explains the concept well but not enough to construct a valid call.

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?

Seven parameters with zero schema description coverage is a heavy burden the description does not carry. It hints at cents ('standing cap') and route ('route allowlist'), but tool, spend_key, credit_key, ttl_minutes and justification are entirely unexplained, and it never clarifies that no parameters are marked required.

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 uses a precise verb and resource: 'Create a pending single-use human-in-the-loop spend escalation approval ticket (sba_*)'. It also scopes the trigger condition (above standing cap or route allowlist), which separates it from routine checkout-style siblings, though no sibling is named explicitly.

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 gives clear when-to-use context: a delegated subagent needing one-time permission beyond its standing cap or route allowlist. It does not state when NOT to use it or point to payment_assistant_decide_approval as the counterpart that resolves the ticket.

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