Skip to main content
Glama
Sign In

BuiltWith

by io.github.builtwith
OverviewDiscussionsAdmin

payment-purchase

Destructive

Charge an existing account's saved Stripe payment method and add account API credits. This is not x402. Requires the separately scoped Agent Billing Key, fixed 2,000-credit increments, and an idempotency 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": {
      "credits": "<credits>",
      "billingKey": "<billingKey>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "payment-purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
creditsYesNumber of account API credits to purchase in fixed increments of 2,000
billingKeyYesSeparately scoped Agent Billing Key from payments.builtwith.com/agent-payment-api-config
idempotencyKeyYesUnique operation identifier; reuse only when retrying the identical purchase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint and openWorldHint, so the bar is lower; the description still adds real substance beyond them by disclosing that this spends real money on a saved payment method and that a special scoped billing key is required. Idempotency reuse semantics are also surfaced. It does not say whether charges are refundable or reversible, which is the one notable gap for a payment tool.

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?

Three short sentences, front-loaded with the core action, then the sibling exclusion, then the prerequisites. No filler and nothing buried at the end.

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?

For a mutating payment tool with no output schema, the description covers the action, prerequisites, and the key scoping requirement, which is most of what an agent needs. It stops short of saying what a successful call returns or how to confirm credits landed, so the agent must discover post-call state itself.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter already carries a description, so the schema does the heavy lifting. The description restates the 2,000-credit increment rule and the billing key requirement without adding format or constraint detail beyond what the schema already provides; baseline 3 applies.

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 opens with a specific verb plus resource: 'Charge an existing account's saved Stripe payment method and add account API credits.' It also explicitly differentiates itself from the x402 purchase family ('This is not x402'), so an agent can route between them without opening either schema.

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?

Prerequisites are stated concretely: a separately scoped Agent Billing Key, fixed 2,000-credit increments, and an idempotency key. It implies the alternative path ('not x402') without naming the sibling to use instead or stating conditions where this tool should not be used, leaving some inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BuiltWith toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources