Skip to main content
Glama

Get credit balance

autoshort_get_credit_balance
Read-onlyIdempotent

Retrieve your current credit balance, monthly allocation, bonus credits, and plan to check available usage before generating or rendering videos.

Instructions

Your current credit balance, monthly allocation, bonus credits and plan. Requires the "credits:read" scope (default in new keys). Free.

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": "autoshort_get_credit_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two things the annotations do not: the required 'credits:read' scope (default in new keys) and the fact that the call is free. That is genuine added context for an agent deciding whether it can call it, though it says nothing about caching or how frequently balances update.

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?

A single front-loaded sentence that enumerates exactly what comes back, followed by the minimal auth and cost note. No filler, no restatement of the title.

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 zero-parameter read with no output schema, the description enumerates the returned fields well enough to set expectations, and it discloses the auth requirement. It falls short of full completeness only in not indicating units, currency, or refresh cadence for the balance figures.

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 no parameter semantics to explain and the schema fully covers this dimension. The description correctly does not waste words restating an empty input object.

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?

States a specific verb and resource implicitly through the return contents: current credit balance, monthly allocation, bonus credits, and plan. It is clear what the tool does, but it does not distinguish itself from near-siblings like get_limits, get_usage_stats, or get_subscription, which plausibly return overlapping billing information.

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 is only implied: you call this when you want to know your balance. There is no statement of when to prefer it over get_limits, get_usage_stats, or get_subscription, and no note that it takes no arguments and is safe to poll. The 'Free' note is a loose hint that it costs nothing, but it is not framed as guidance.

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