Skip to main content
Glama

Check credit and usage

get_account
Read-onlyIdempotent

Check account balance, plan, usage limits, and whether file or live transcription can start now. Use before long or live jobs or after credit or quota errors to see remaining capacity.

Instructions

Check the account's credit and usage: the balance left, the plan, whether a new file or live transcription would start now (and what would refuse it), and this period's limits. Use: before a long or live transcription, after an insufficient_credit or quota_exceeded error, or to tell the user what they have left. Prices per minute are in create_transcription and start_broadcast; adding credit happens at topUpUrl, in a browser. Arguments: none. Behaviour: free and read-only; nothing is cached, each call reads the account as it is at that moment, including a live run still being billed. Calling it changes nothing and spends nothing. Gives rate_limited (with retryAfterS) past 600 calls a minute per API key. Returns: billingEnabled; plan (id, name, kind) or null; balance in US dollars (negative while a plan lets a running transcription continue below zero); canStart and startBlock (no_credit or hourly_limit, null when it starts) for a file; canStartLive and startBlockLive (also concurrency) for a live one; running, concurrentLimit, createdLastHour and createLimit (null means unlimited); period (start, end); monthlyCredit when a plan grants one; usageCap (amount, period, used, resetsAt) when this API key has a spending cap; topUpUrl; for a signed-in person termsAccepted, and while false acceptUrl: a page where they accept the Terms of Service and Privacy Policy themselves, once, before their first transcription. Errors: rate_limited (with retryAfterS); forbidden for a token without the read scope.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: states the call is free, that nothing is cached and each call reads live state including an in-flight billed run, and that negative balance can occur while a plan permits a run below zero. It also discloses the rate limit (600 calls/minute per API key, returning rate_limited with retryAfterS) and a forbidden error for tokens lacking the read scope — operational details the annotations do not carry.

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 Use, Behaviour, Returns, and Errors sections, so an agent can scan to what it needs. The Returns block is a single dense run-on enumeration that is hard to parse in one pass, which costs some readability even though nearly every field mentioned carries decision-relevant meaning.

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?

There is no output schema, so the description carries the full burden of return-value documentation and discharges it thoroughly — field-by-field semantics for canStart/startBlock, concurrency limits, usageCap, topUpUrl, and the Terms-of-Service acceptance flow. Errors and rate limiting are also covered, so nothing an agent needs in order to interpret results is missing.

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

Parameters5/5

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

Zero-parameter tool, and the description confirms this explicitly with "Arguments: none" rather than leaving it implicit. The schema is empty and additionalProperties is false, so there is no ambiguity to resolve beyond that statement.

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+resource ("Check the account's credit and usage") and enumerates exactly what is covered: balance, plan, start eligibility for file and live transcription, and period limits. It also separates itself from siblings by pointing to create_transcription and start_broadcast for per-minute prices, so an agent can distinguish it from the transcription tools.

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

Usage Guidelines5/5

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

An explicit "Use:" clause gives three triggering situations (before a long/live transcription, after insufficient_credit or quota_exceeded, or to report remaining balance). It also routes the agent away from this tool for adjacent needs — pricing lives in create_transcription/start_broadcast and adding credit happens at topUpUrl in a browser — which is exactly the when-not/alternative guidance the dimension asks for.

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