Skip to main content
Glama

Kubeez

get_balance

Read-onlyIdempotent

Scope: read:balance. Check the user's current credit balance. Always call this before generate_media or generate_music to avoid 'insufficient credits' errors. Returns available credits; each generation consumes credits based on the model (see get_models for cost_per_generation).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the marginal burden is low. The description still adds useful context beyond them: credits are consumed per generation and cost depends on the model, with a pointer to get_models for cost_per_generation. It does not discuss caching or balance staleness, which keeps it just short of a 5.

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 tight clauses, each doing distinct work: scope, purpose, mandatory call ordering, and the credit-cost model with a cross-reference. The scope constraint is front-loaded and nothing is repeated.

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?

For a parameterless read with an output schema and full annotation coverage, this description supplies everything an agent needs: what it returns, when to call it, and why the result matters for downstream generation calls.

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 the schema baseline is 4 and there is nothing further a description could clarify. The description correctly spends no words on arguments.

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 ('Check the user's current credit balance') and pairs it with an explicit auth scope ('Scope: read:balance'). An agent can immediately distinguish this read-only balance lookup from the sibling generation tools it references.

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?

Gives an explicit directive for when to call it ('Always call this before generate_media or generate_music') and the failure mode it prevents ('insufficient credits' errors). It names the concrete alternatives rather than leaving the agent to infer them.

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