Retrieve an account's balance page data, including available plans, the current subscription, and payment history, to review billing status and past transactions.
Страница «Баланс» целиком: тарифы, текущая подписка, история платежей.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| account | No |
Changes observed during successful MCP inspections.
v0.9.13Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description successfully adds context by specifying the types of information exposed (tariffs, history, subscription), which enhances the understanding of the tool's output data beyond what the general 'readOnlyHint' annotation provides.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is concise and highly effective. It uses minimal words to summarize a complex page view, placing the most critical information immediately at the beginning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The high-level functional purpose is complete, but the lack of detail regarding the mandatory parameters makes the tool definition incomplete for practical execution by an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Despite being a 2-parameter tool, the description is completely silent on how the parameters ('page' and 'account') are used or what values they represent. Given 0% schema coverage, the description must define these semantics, but it fails to do so.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description provides an extremely clear definition of the tool's purpose: viewing the entire 'Balance' page. It specifically lists the included elements like tariffs, current subscription, and payment history, leaving no doubt about its function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description focuses entirely on describing the tool's functionality and content, providing no guidance on when to use it versus alternatives or under what operational conditions it is most appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.