LyricPatch

prepare_credit_purchase

Idempotent

Prepare a credit purchase, without paying yet. 40=$1.99,100=$4.99,400=$14.99,1000=$29.99.

    Gives an account-bound pay_url. An authorized x402 wallet client POSTs to that URL,
    reads PAYMENT-REQUIRED, then retries with PAYMENT-SIGNATURE for USDC on Base mainnet.
    Never send wallet private keys to this tool. Browser Stripe checkout is also available.

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": {
      "pack_id": "<pack_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "prepare_credit_purchase"
  }
}

Input Schema

Name	Required	Description	Default
`pack_id`	Yes
`idempotency_key`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare mutating-but-non-destructive and idempotent, and the description adds substantial value beyond them: it discloses the account-bound pay_url output, the x402 PAYMENT-REQUIRED/PAYMENT-SIGNATURE handshake, USDC on Base mainnet, and an explicit security warning ('Never send wallet private keys to this tool'). It doesn't state the pay_url's lifetime/expiry behavior, so a 4.

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?

Purpose is front-loaded in the first sentence and the security warning is prominent. The pricing list is compressed and the flow explanation is dense but earns its place; minor slack only.

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?

With an output schema present, return-value detail is not required, and the description covers the payment flow and safety constraints well. The main gap is the undocumented idempotency_key, which an agent must supply without any guidance.

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 description coverage is 0%, so the description must compensate. The pricing table (40=$1.99 ... 1000=$29.99) concretely maps the four pack_id enum values to their cost, which is genuinely additive, but idempotency_key receives no explanation of its purpose or reuse semantics.

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 (prepare) and resource (credit purchase) with a scoping qualifier ('without paying yet') that clarifies the tool does not complete payment. No sibling tool covers credit purchasing, so it is easily distinguished from the project/edit/upload tools in the sibling list.

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?

Gives clear context: prepare first, then an authorized x402 wallet client POSTs to the returned pay_url to actually pay, and it names an alternative path ('Browser Stripe checkout is also available'). It doesn't spell out when to prefer one payment path over the other or how it relates to get_payment, so it stops short of a 5.

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

All LyricPatch tools Inspect

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.