Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Saldo com uma pessoa

get_person_balance
Read-onlyIdempotent

Calculate a person's net financial balance for a specified period to determine if they owe money or have credit, including recorded settlements.

Instructions

Retorna o saldo financeiro com uma pessoa no período: quanto ela deve ou tem de crédito, e os acertos registrados.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personId": "<personId>"
    },
    "name": "get_person_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo
personIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the result is period-scoped and includes settlements, but says nothing about what happens when the period is omitted or how a zero/absent balance is reported.

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?

A single sentence with the core verb and scope front-loaded and no filler. It could be tightened only by adding rather than removing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description is close to adequate: it conveys what the balance result contains. However, the missing period format/default and the undefined sign convention for 'deve ou tem de crédito' leave an agent guessing at how to call it and how to read the response.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it only partially does: 'no período' implies the period parameter but never states its required YYYY-MM format or the default when omitted. The required personId is not explained at all beyond the prepositional phrase 'com uma pessoa'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Retorna o saldo financeiro com uma pessoa'), scopes it to a period, and names the payload contents (debt/credit amount plus registered settlements). It is clear enough to distinguish from list/settlement-mutation siblings, though it does not explicitly separate itself from get_person_summary or get_person_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites (e.g. an existing connection with the person), and no reference to alternatives such as get_person_summary or get_person_report. The agent must infer the use case entirely from the resource name.

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