Skip to main content
Glama

Whizbrew

Check credit

get_balance
Read-only

The prepaid Whizbrew credit of this account.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only that the credit is 'prepaid' and account-scoped, with nothing about what the returned balance represents (available vs. pending credit), its currency, or whether the call has any side effects or costs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short line with zero padding, but it is a noun phrase rather than a sentence and is not front-loaded with an action verb, so brevity comes at the cost of clarity. Nothing is wasted, but nothing is structured for fast scanning either.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with full annotation coverage, little is required, and the annotations plus empty schema make the invocation unambiguous. However, with no output schema, the description should have stated what the balance result looks like (numeric amount, currency, prepaid vs. total), and it does not.

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 meaning for the description to convey and the baseline applies. The description correctly implies the account is determined by the current session/credentials rather than an argument, which is a small but useful clarification.

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

Purpose3/5

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

The fragment 'The prepaid Whizbrew credit of this account' identifies the resource (account-scoped prepaid credit) but supplies no verb and no explicit statement that the tool retrieves a balance. It is interpretable via the title 'Check credit' but the description alone leaves the action implicit, and it does not distinguish itself from sibling read tools such as get_quote.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no precondition, and no mention of the obvious alternative (add_money) for the opposite operation. An agent must infer that this is the read path for balance and that add_money is the write path, with nothing in the text to confirm it.

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