consultar_saldoRetrieve the available and blocked balances of a PushinPay account to monitor funds and identify temporarily held amounts; values are returned in cents.
Retorna o saldo disponível e o valor bloqueado da conta PushinPay. Todos os valores são em centavos (ex.: 1000 = R$ 10,00). blocked_balance são valores temporariamente retidos (ex.: prevenção/segurança).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description provides highly specific behavioral information not in the schema, notably the unit of measurement (all values are in cents) and a definition of the 'blocked_balance' mechanism.
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 description is exceptionally concise, using two sentences to cover purpose, value convention, and behavioral definitions without any redundancy.
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?
For a zero-parameter, read-only tool, the description is very complete, detailing what the agent should expect in the response regarding units and key field definitions.
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?
Since the parameter count is zero, the description adds essential semantic meaning regarding the nature of the data returned (e.g., explaining the meaning of 'blocked_balance' and the cent conversion).
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 uses a specific verb ('Retorna') and identifies the exact resources being checked: 'saldo disponível' and 'valor bloqueado' for the PushinPay account.
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?
Although it does not explicitly state when to use this versus 'consultar_transacao', the fundamental difference between checking a current balance versus reviewing transaction history is strongly implied by its stated purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.