VideoGen

Quote credit purchase

create_billing_order

DestructiveIdempotent

Prepare a one-time credit quote for an eligible active USD subscriber, without paying or generating. Use a fresh UUID for a new quote and reuse it for quote retries. Show seller, beneficiary team, credits, total, currency, taxes, fees, expiry and refund terms before asking approval. Existing accounts and credentials have billing access off until explicitly enabled in VideoGen.

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>",
      "credits": "<credits>"
    },
    "name": "create_billing_order"
  }
}

Input Schema

Name	Required	Description	Default
`credits`	Yes
`orderId`	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.2/5.0

Behavior4/5

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

Beyond the annotations, it discloses that the operation does not pay or generate, explains retry behavior, requires pre-approval disclosure of commercial terms, and states the default-off billing-access prerequisite. It does not explain what persistent order state is created or why the operation carries destructiveHint=true, leaving some side-effect ambiguity.

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?

Four compact sentences front-load the quote-only purpose, then cover retry behavior, approval requirements, and access prerequisites. The long list of terms to display is operationally useful, and no sentence merely repeats the title or structured fields.

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 two-parameter tool with an output schema, the description covers most invocation needs: eligibility, access enablement, idempotency, side-effect limits, and approval. It would be more complete with an explicit handoff to complete_billing_order and clarification of the destructive annotation and behavior for ineligible or non-USD subscribers.

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?

With 0% schema description coverage, the fresh-versus-reused UUID guidance gives orderId substantial meaning and usefully supports the idempotent annotation. The credits parameter is only implicitly identifiable as the desired quote amount; the description adds no further semantics for it, although the schema supplies numeric bounds and increments.

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?

“Prepare a one-time credit quote” states a specific action, resource, and scope, further limited to an eligible active USD subscriber. “Without paying or generating” distinguishes it from payment completion and generation siblings, even though those siblings are not named.

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?

It gives concrete usage context: billing access must be enabled, a fresh UUID starts a new quote, the same UUID is reused for retries, and terms must be shown before approval. It does not explicitly direct agents to complete_billing_order after approval or get_billing_order for inspection, so some lifecycle routing remains inferential.

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.