Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Fluxo de caixa da conta

get_account_cash_flow
Read-onlyIdempotent

Retrieves an account's daily cash flow for a month, including opening balance, daily entries, out-of-month amounts, and monthly history to track balances and transactions.

Instructions

Retorna o fluxo de caixa diário de uma conta em um mês: saldo inicial, lançamentos do dia, valor fora do mês e histórico mensal.

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": {
      "id": "<id>"
    },
    "name": "get_account_cash_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID da conta.
periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.4/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 covered. The description adds value by disclosing the shape of the result (initial balance, day entries, out-of-month amount, monthly history), which matters since there is no output schema, but it says nothing about permissions, data freshness, or behavior when the period is omitted.

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 front-loaded sentence with no filler; the resource and scope come first and the returned fields follow. It could be tightened only marginally.

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?

For a read-only, two-parameter tool with no output schema, the description does the important work of describing the return payload. However, it leaves the optional 'period' parameter's format and default behavior unexplained, which is a real gap for correct invocation.

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?

Schema coverage is 50%: 'id' is documented but 'period' has no description. The phrase 'em um mês' partially compensates by implying period is a month granularity, consistent with the YYYY-MM pattern, but the format and the default when period is absent (it is not required) are never stated.

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?

States a specific verb ('Retorna') and resource ('fluxo de caixa diário de uma conta em um mês') and enumerates the returned components (saldo inicial, lançamentos do dia, valor fora do mês, histórico mensal). This clearly separates it from generic siblings like get_account or get_dashboard_overview, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it is for retrieving an account's daily cash flow for a given month. There is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no pointer to a sibling for related views such as trends or distribution.

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