Skip to main content
Glama

Баланс API

get_balance
Read-onlyIdempotent

Возвращает баланс API аккаунта (общий для всех ключей и MCP), в рублях. balance: остаток, ₽; spent_month: потрачено в этом месяце, ₽; request_price: цена запроса за каждые начатые request_unit_mb МБ входа (файл до 10 МБ — один запрос); included_remaining: сколько обычных запросов в текущем месяце тарифа ещё входит в тариф Бизнес (месяц — от даты покупки, обновятся в included_resets_at; расходуются раньше баланса; у других тарифов 0).

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.2/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 description is free to add real behavioral context — that the balance is shared across all keys, that plan-included requests are spent before the balance, that the billing month runs from the purchase date and resets at included_resets_at, and that non-Business plans report 0. That is genuine value beyond structured fields, though billing edge cases (what happens on negative balance or mid-cycle tier change) are not addressed.

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 dense and front-loaded: the purpose sentence comes first, followed by a semicolon-delimited field glossary. It is efficient, but the field-by-field definitions of balance, spent_month, request_price and included_remaining partly duplicate an output schema that is declared present, so some text does not fully earn its place.

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 zero-parameter read tool with full annotation coverage and an output schema, nothing needed to invoke it correctly is missing, and the shared-balance and consumption-order semantics go beyond what the annotations and schema convey. The description is complete for its complexity.

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 there is nothing to disambiguate and the baseline of 4 applies. The description's explanation of request pricing units belongs to return values, not inputs, and an output schema already exists to carry it.

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 first sentence names a specific verb and resource ("Возвращает баланс API аккаунта") and states the scope (shared across all keys and MCP) and currency (rubles). This clearly separates it from every sibling tool, all of which are file-conversion or PDF-editing operations.

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: the tool is the natural way to check remaining funds before making billable requests, and the note that included requests are consumed before the balance hints at the check-before-use pattern. There is no explicit "use this when" or "do not use when" statement, though in fairness there is no competing sibling to route away from.

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.