VideoGen

Get billing order

get_billing_order

Read-onlyIdempotent

Read the original order's current payment and credit fulfillment status. Check this before retrying an uncertain purchase. Paid pending fulfillment means payment settled but credits are not yet confirmed. This read never collects money or grants credits.

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

Input Schema

Name	Required	Description	Default
`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?

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds real value beyond them by explaining the domain semantics of 'paid pending fulfillment' and by asserting 'never collects money or grants credits', which is the exact question an agent has before retrying a purchase.

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 short sentences, front-loaded with the purpose, then the usage trigger, then the status interpretation, then the side-effect disclaimer. No sentence is redundant and the ordering matches how an agent decides whether to call the tool.

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 single-parameter read with an output schema present, the description covers purpose, call trigger and the meaning of the key status value, so it need not describe return fields. Only minor gaps remain, such as error behavior for a missing or foreign orderId.

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 one parameter at 0% schema description coverage, the description must compensate. It adds the meaningful qualifier 'original order's', implying the orderId should reference the original attempt rather than a retry, but it never spells out where that orderId comes from or what happens on an unknown id.

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 ('Read the original order's current payment and credit fulfillment status') and implicitly distinguishes itself from mutation siblings like create_billing_order, complete_billing_order and cancel_billing_order by framing itself as a read of existing state.

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 explicit when-to-use guidance: 'Check this before retrying an uncertain purchase.' That is a concrete trigger condition rather than a vague suggestion. It stops short of naming which sibling to call instead for the retry itself, so it is not a full when/when-not/alternatives statement.

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.