Skip to main content
Glama

Singing Pet

Get credit balance

get_credit_balance
Read-onlyIdempotent

How many API credits are left. One credit renders one video. Check this before creating a video if you want to fail early rather than on a 402.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/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 genuine value beyond that by explaining the credit-to-video exchange rate and the 402 failure mode that follows an empty balance. However, it says nothing about the shape of the response (a bare number vs. an object with a limit), which is the one behavioral gap left for a zero-param read.

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?

Three short sentences: what it returns, what a credit means, and when to call it. The most important fact, the balance, is front-loaded and nothing is padded or repeated.

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 full annotation coverage and no output schema, the definition covers purpose, unit of measure, and the reason to call it. The only omission is any hint about the return value's form, which is a minor gap given the name and the explicit 'how many' framing.

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 no parameters, which sets the baseline at 4. The description correctly adds no parameter guidance because there is nothing to parameterize, and it uses the space instead to define the unit of the returned value.

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 states a concrete read: how many API credits remain, plus the unit semantics ('one credit renders one video'). That makes the resource and its meaning unmistakable, and no sibling in the list could be confused with a balance check, though the description never explicitly distinguishes itself from them.

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 when-to guidance: check before creating a video if you want to fail early rather than on a 402. That is a real precondition and ordering recommendation rather than a vague suggestion. It does not enumerate alternatives, but no plausible alternative exists among the siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources