Skip to main content
Glama

account_balance

Read-only

Check prepaid credit, remaining free trial calls and company lookups, and monthly usage before paid KYB calls to see whether requests will be free, charged, or refused.

Instructions

Check the prepaid balance, the free trial call and the free company lookups left, and this month's calls. Free (no charge).

    Call it before a batch of paid calls to know whether they will be
    free, paid or refused (402). Prices: company_lookup and
    company_officers EUR 0.01 when found (100 free per account),
    kyb_findings / adverse_media EUR 0.50, kyb_run_submit EUR 6.00. A new
    account's first findings or report call is 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": "account_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare the tool is read-only and non-destructive, and the description adds behavior that annotations do not cover: the call is free, the check predicts free/paid/402 outcomes, and it lists per-call prices and the free-allowance rules. This extra context is exactly what an agent needs before spending credits.

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?

The description is front-loaded with what the tool returns, then when to call it, then the pricing details. Every sentence is useful, but the pricing list is somewhat dense and could go stale. The structure is sound, though not maximally tight.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, timing, cost model, and refusal behavior. Minor gaps remain, such as what the 402 response looks like or how the free trial is counted. It is nearly complete for a zero-parameter read tool.

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, so parameter semantics are moot; the baseline is 4. The description adds no parameter information because there is none to add. That is appropriate given a zero-argument schema.

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?

The description states specific resources: prepaid balance, free trial calls, free company lookups remaining, and this month's calls. No sibling tool reports balances or usage, so the tool is clearly distinguishable. The verb-plus-resources framing lets an agent identify it immediately.

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?

It says explicitly when to call it: before a batch of paid calls, to learn whether those calls will be free, paid, or refused with a 402. It names the relevant paid siblings (company_lookup, company_officers, kyb_findings) and ties the check to a concrete decision. That is unambiguous when-to-use guidance.

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