VideoGen

Complete approved credit purchase

complete_billing_order

DestructiveIdempotent

Sensitive write: pay only this exact quoted order after explicit approval of its complete terms. Requires a compatible wallet supplying a scoped credential through secure request metadata. Never ask the user to paste payment credentials or put them in arguments. Reuse the original order, revision and idempotency key after an uncertain outcome. A paid result is separate from fulfilled credits. No recurring subscriptions.

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": {
      "orderId": "<orderId>",
      "revision": "<revision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "complete_billing_order"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	Yes
`revision`	Yes
`idempotencyKey`	Yes

Output Schema

Name	Required	Description
`state`	Yes	Payment and credit fulfillment state.
`seller`	No	Seller of record.
`teamId`	No	Beneficiary team id.
`credits`	No	Credits purchased by this order.
`orderId`	Yes	Client-generated order UUID.
`currency`	No	Order currency.
`revision`	Yes	Quote revision to approve when completing.
`taxMinor`	No	Tax in minor units.
`teamName`	No	Beneficiary team name.
`expiresAt`	No	Quote expiry in Unix seconds.
`feesMinor`	No	Fees in minor units.
`receiptUrl`	No	Receipt URL once paid.
`totalMinor`	No	Total to approve, in minor units.
`refundTerms`	No	Refund terms to show before approval.
`refundStatus`	No	Refund request status, separate from the payment state.
`discountMinor`	No	Discount in minor units.
`retryGuidance`	No	How to safely resolve or retry this order.
`subtotalMinor`	No	Subtotal in minor units.
`verificationUrl`	No	Secure verification continuation for the purchaser, when required.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior3/5

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

Goes well beyond the annotations by disclosing credential handling through secure request metadata, the idempotent-reuse rule for uncertain outcomes, and the distinction between 'paid' and 'fulfilled credits'. However, it does not say what a failed payment leaves behind or whether partial states are possible, which matters given destructiveHint=true.

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?

Front-loaded with 'Sensitive write' and each sentence carries an actionable rule rather than filler. The telegraphic style ('pay only this exact quoted order', 'A paid result is separate from fulfilled credits') is dense but readable.

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

Completeness5/5

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

Output schema exists, so return values need not be explained, and the definition still supplies the one interpretive point an agent needs (paid vs. credits fulfilled). For a three-required-parameter mutation, the approval, credential-handling, and retry rules cover what is needed to invoke it safely.

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 carry the load; it names all three parameters in the reuse sentence and conveys that revision and idempotencyKey are bound to the original order. It adds no format or constraint guidance beyond the schema (UUID orderId, 16-char minimum key), so the meaning added is about lifecycle rather than value 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 and resource ('pay only this exact quoted order') plus scope ('this exact'), which cleanly separates it from create_billing_order, cancel_billing_order, and get_billing_order in the sibling set. An agent can identify the operation without opening the 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?

Gives clear preconditions ('after explicit approval of its complete terms') and an explicit retry rule ('Reuse the original order, revision and idempotency key after an uncertain outcome'), plus a scope exclusion ('No recurring subscriptions'). It stops short of naming create_billing_order as the required predecessor, leaving that relationship to be inferred from the sibling list.

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

All VideoGen 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.