Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_quote

Read-onlyIdempotent

Preflight quote any single HTTP 402 capability or multi-step agent plan (items) and evaluate whether your Stripe spend key (or delegated subagent key) can auto-execute within balance, per-order cap, daily cap, total cap, and 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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNo
itemsNo
orderNo
routeNo
quantityNo
spend_keyNo
credit_keyNo
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the enumerated evaluation criteria: balance, per-order cap, daily cap, total cap and route allowlist, plus the delegated-subagent-key case. It does not say what the verdict looks like or what happens on denial, so it is strong but not complete.

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 dense sentence with zero filler and the core verb front-loaded. The parenthetical '(items)' and nested alternatives make it a run-on, but nothing is superfluous.

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 read-only tool with a 25-element nested plan array, no output schema and 0% parameter documentation, the description should at minimum explain the request shape and the nature of the quote result. It gives the policy dimensions but leaves an agent unable to construct a valid call or anticipate the response.

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 8 parameters, including a nested items array with order, route, quantity and capability_id. The description only gestures at 'items' and 'spend key (or delegated subagent key)'; it never explains order, route, quantity, credit_key, capability_id, or the relationship between the top-level tool/items and nested duplicates, so it leaves the bulk of the schema unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Preflight quote') plus the two resources it covers ('any single HTTP 402 capability or multi-step agent plan (items)') and the decision it renders (auto-execute or not). This clearly separates it from execution-oriented siblings like payment_assistant_checkout.

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?

'Preflight' implies use before committing to a purchase, and the mention of a single capability vs. an items plan implies two modes. But there is no explicit when-to-use/when-not, no statement that checkout follows an approved quote, and no guidance on choosing between the single-item and items forms.

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