Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_delegate_key

Mint a budget-capped, route-scoped, time-boxed child X402 spend key (sbk_*) for a subagent or workflow from your master Stripe-funded account.

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

Input Schema

NameRequiredDescriptionDefault
labelNo
agent_idNo
spend_keyNo
ttl_hoursNo
credit_keyNo
allowed_routesNo
max_order_centsNo
daily_budget_centsNo
total_budget_centsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the safety burden is largely covered. The description adds useful semantics beyond that: the returned key is prefixed sbk_ and carries budget, route, and time bounds. It omits what happens on repeated calls, whether the minted key is retrievable later, and whether master credentials must be supplied in the call, which is material for a 9-parameter mint operation.

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?

One front-loaded sentence with zero filler; the verb and the artifact come first, qualifiers follow. It is dense with hyphenated compounds but every clause carries information, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 9-parameter credential-minting tool with no output schema and no parameter documentation, so more should be said about inputs and about the returned key. However, the description does correctly convey the core mental model of the operation, positioning it as a strong but incomplete summary.

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% across 9 parameters, so the description must carry the load, and it only gestures at three of them (budget-capped, route-scoped, time-boxed). The most consequential inputs, credit_key, spend_key, agent_id, and label, get no explanation at all, and the notable fact that no parameters are required is not addressed.

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 concrete verb ('Mint') and a highly specific resource ('child X402 spend key (sbk_*)'), plus the three defining scope attributes: budget-capped, route-scoped, time-boxed. That is enough to separate it from the obvious sibling payment_assistant_revoke_key without opening a schema, 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 Guidelines2/5

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

It says the key is minted for a subagent or workflow from a master Stripe-funded account, which implies the context, but it never states prerequisites (does the master account need funding or prior setup?), nor when to prefer this over checkout or request_approval, nor the lifecycle step (revoking via payment_assistant_revoke_key).

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