Ania

Wallet balance and limits

get_balance

Read-only

The user’s Ania wallet balance (prepaid Ania credits, shown in US$ for non-Portuguese users, 1 credit = R$1), this connection’s monthly spending cap and how much of it is used. Call before quoting/buying or when the user asks what they have or can spend. To add credits, use top_up.

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

Name	Required	Description	Default
`language`	No	The user's language as a BCP-47 tag (e.g. 'en', 'en-US', 'pt-BR', 'es'). Replies and prices follow it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish a safe, closed read (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description still adds real context: the US$/credit conversion, the display rule for non-Portuguese users, and the fact that spend is scoped per connection. It stops short of describing the return shape or what happens when no wallet exists, which matters given there is no output schema.

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?

Two tight sentences: the first defines the returned data, the second defines when to call it and which sibling to use otherwise. The monetary and conversion details are parenthetical and do not interrupt the front-loaded statement of purpose.

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?

For a single optional-parameter, read-only tool with full schema coverage, the description covers what is returned conceptually, when to call it, and the currency logic. Without an output schema it could still say more about the returned fields' form or failure cases (e.g., no wallet yet), leaving a minor gap.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning about the language parameter's effect: prices and displayed currency (US$ for non-Portuguese users) follow it. That goes beyond the schema's generic 'Replies and prices follow it' note and explains the credit-to-real conversion.

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 names the exact resource and the three values returned: prepaid Ania credits, the connection's monthly spending cap, and how much of it is used. It also distinguishes the tool from the sibling that changes the balance by naming top_up for adding credits.

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?

Explicit triggers are given: call before quoting or buying, or when the user asks what they have or can spend. The alternative path is spelled out ('To add credits, use top_up'), so the agent can route between this and the sibling without inference.

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

All Ania tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?