VideoGen

Get billing account

get_billing_account

Read-onlyIdempotent

Read the selected team's usable credit balance and explicitly delegated billing access. Connecting an account alone grants no billing access. This read makes no payment or permission changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_billing_account"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`teamId`	Yes	Team whose credits and billing access apply.
`currency`	No	Purchase currency (usd).
`teamName`	No	Team display name.
`creditPack`	No	Allowed credit quantities for a new order.
`canPurchase`	Yes	Whether this credential may buy credits right now.
`accessExpiresAt`	No	When delegated billing access expires, in Unix seconds.
`creditsRemaining`	Yes	Usable credit balance.
`purchaseLimitMinor`	No	Per-purchase limit in minor currency units (cents).
`purchaseRestriction`	No	Why purchases are unavailable, when canPurchase is false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: that account connection alone confers no billing access and that this call makes no payment or permission changes, which matters for an authorization-sensitive resource.

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?

Three short sentences, front-loaded with the resource and scope, with no filler. The closing sentence partially restates the read-only annotation, but it adds the 'no permission changes' nuance rather than repeating verbatim.

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 zero parameters, an output schema covering return values, and full annotation coverage, the description only needs to convey scope and safety, which it does. The sole residual gap is that 'selected team' is never explained, which is a minor omission for a context-derived selector.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The only ambiguity is which team is 'selected', which the description leaves to session context but never contradicts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Read the selected team's usable credit balance and explicitly delegated billing access'), which tells an agent exactly what data comes back. It is distinguishable from billing siblings such as get_billing_order and request_billing_refund, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: the agent learns this is a pure read of balance and delegated access, and that merely connecting an account grants nothing. There is no explicit 'use this instead of get_billing_order when...' routing, so the agent must infer which billing tool answers which question.

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.