hubris-mcp

Get account balance

balance_get

Read-onlyIdempotent

Retrieves the current account balance in rubles, including an exact integer string for calculations and a formatted value for display.

Instructions

Current balance of the Hubris account the API key belongs to, in rubles.

Worth checking before a long or expensive run: requests are refused once the balance is spent. The balance can go slightly negative — one operation is allowed to overdraw it, and the next one is refused.

Two representations of the same number come back. Use balanceKopecks for arithmetic and comparisons — it is an exact integer string. Use balanceRub for display.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`balanceRub`	Yes	Balance in rubles as a decimal string, e.g. "1240.55". Negative when the account is overdrawn.
`balanceKopecks`	Yes	The same balance in kopecks as an integer string. Use this one for arithmetic: it is exact, while the ruble string is for display.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (read-only, idempotent), the description adds behavioral context: requests are refused when balance is spent, and the account can go slightly negative. This goes beyond the annotation hints.

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?

The description is concise and well-structured, with two clear paragraphs. It avoids unnecessary details and delivers the essential information efficiently.

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?

The description explains the output representations (balanceKopecks for arithmetic, balanceRub for display) and the behavior regarding balance depletion, making it complete for a simple no-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, and schema coverage is 100% (empty). The description does not add parameter-related information, but since there are none, the baseline of 3 is appropriate.

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 clearly states the tool retrieves the current account balance, using the verb 'get' and specifying the resource. It distinguishes itself from siblings by the explicit focus on balance, though not directly comparing to others.

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?

Provides explicit guidance on when to use the tool: 'Worth checking before a long or expensive run'. Also explains the behavior of balance going negative, which informs usage decisions.

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

Install Server