Skip to main content
Glama

Wisely x402 Agent-Payment Infrastructure

x402_gift_card_merchant_quote

Quote any Bitrefill-supported merchant gift-card purchase after product details are fetched, using $0.75 + 1% plus explicit route/network costs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
typeNo
assetNo
inputNoPublic-safe request body/input for a hosted service or endpoint. Never include secrets, raw cards, wallet keys, passwords, or private account tokens.
itemsNo
queryNo
sinceNo
itemIdNo
acceptsNo
contentNoPublic-safe creator content for preview/import. Do not include secrets, private student data, or copyrighted material you do not own.
networkNo
audienceNoOptional audience hint for wisely_start_here / wisely_get_playbook / wisely_agent_instructions.
payoutIdNo
platformNoOptional OS/platform hint for local bridge setup, e.g. windows, mac, linux.
amountUsdNo
creatorIdNo
fromAssetNo
localPortNoOptional localhost port for the local commerce bridge MCP server. Defaults to 4027.
receiptIdNo
sellerUrlNoThird-party x402 paid resource URL to probe for HTTP 402 payment requirements.
serviceIdNo
sessionIdNoWallet handoff/payment session id returned by x402_wallet_handoff/connect_wallet.
toAddressNo
sellerBodyNoPublic-safe POST body for an external x402 seller. Never include cookies, bearer tokens, wallet secrets, private keys, card data, or account passwords.
contentTypeNo
fromAddressNo
fromNetworkNo
manifestUrlNo
paidActionsNo
endpointSlugNo
sellerMethodNoUse POST for paid APIs that need a public-safe body before returning 402.
payoutAddressNo
serverJsonUrlNo
idempotencyKeyNoStable retry key for paid invokes and wallet handoff sessions.
paymentPayloadNo
includeExamplesNoSet false to request a shorter playbook response.
fromTokenAddressNo
preferredNetworkNoPreferred payment network for wallet handoff, e.g. eip155:8453 or base.
defaultEntitlementNo
paymentRequirementNo
paymentRequirementsNo
returnSignedPaymentNoAlias for includeSignedPayment.
includeSignedPaymentNoFor x402_payment_session_status, include the signed X-PAYMENT payload when the user has signed.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the cost structure ($0.75 + 1% plus route/network costs) and a prerequisite (product details fetched). This is meaningful behavioral context for an agent, though it does not mention side effects, return format, or authorization needs. The 'quote' semantics imply non-mutating behavior.

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 sentence efficiently conveys purpose, precondition, and pricing. There is no filler, redundancy, or unnecessary detail, making it easy to parse.

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?

Given the tool's complexity (43 parameters, no output schema, nested objects), the description is too terse. It does not explain input requirements, response shape, error conditions, or how this tool relates to other gift-card tools. The pricing and precondition are useful but insufficient for an agent to confidently invoke the tool.

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 coverage is only 33% with 43 parameters, and the description provides no parameter-specific guidance. It does not indicate which fields are required for a quote (e.g., url, amountUsd, network), nor how the pricing formula maps to inputs. The phrase 'after product details are fetched' hints at a precondition but does not connect to any parameter, failing to compensate for the low schema coverage.

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?

The description clearly states the tool's function: 'Quote any Bitrefill-supported merchant gift-card purchase' – a specific verb (quote), resource (merchant gift-card purchase), and a unique scoping (Bitrefill-supported). It also adds a condition ('after product details are fetched') and the pricing formula, distinguishing it from sibling quote tools like x402_gift_card_commerce_quote.

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?

The description provides a clear context: use after product details are fetched, and it specifies the pricing model. It does not explicitly name alternatives or when not to use it, but the mention of 'Bitrefill-supported' and the sequencing condition imply the intended workflow.

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.

TDQS

C2.5/5.0
Disambiguation1/5

The tool set is riddled with aliases and duplicates (e.g., start_here, wisely_start_here, get_playbook, agent_instructions, readme, wisely_get_playbook, wisely_agent_instructions all serve the same purpose). Dozens of status tools and setup aliases overlap heavily, making it nearly impossible for an agent to select the right tool without testing.

Naming Consistency2/5

There is a mix of x402_ and wisely_ prefixes, plus unprefixed generic tools like start_here, connect_wallet, and readme. Alias names diverge from their canonical names (e.g., connect_wallet vs x402_wallet_handoff), and while snake_case is consistent, the pattern is not predictable across the full set.

Tool Count1/5

65 tools is far beyond what is typically appropriate for an MCP server (3-15). The count is inflated by aliases and many near-identical status/check tools, creating a bloated surface that is unnecessarily heavy and confusing for agents.

Completeness3/5

Core payment, wallet, receipt, and quote workflows are well covered. However, there are significant gaps in actual builder endpoint management (only handoff instructions, no direct create/update/delete tools) and creator catalog lifecycle (preview and onboarding handoff but no publish/update/delete tools), leaving some workflows as dead ends.