Skip to main content
Glama
Open Finance Plugin MCP

Open Finance Plugin MCP

by Moreti2002

gastos_por_categoria

Read-onlyIdempotent

Calculates total spending by category and currency over a date range, sorted highest to lowest. Exclude categories to avoid double-counting transfers and credit card bill payments.

Instructions

Soma das saidas (DEBIT) por categoria e moeda no periodo, da maior para a menor. Use ignorar_categorias para tirar transferencias entre contas proprias e pagamento de fatura, que senao contam o mesmo gasto duas vezes.

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": {
      "desde": "<desde>"
    },
    "name": "gastos_por_categoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
ateNo
desdeYes
ignorar_categoriasNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful behavior beyond that: only DEBIT outflows are counted, results are grouped by category and currency, and sorted descending. The double-counting caveat for transfers and invoice payments is a genuine non-obvious behavioral trait.

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 sentences, no filler. The core operation and ordering come first, and the caveat about excluding categories follows where it is most actionable.

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?

An output schema exists, so return-shape explanation is not needed, and the description covers the operation, grouping, ordering, and the main data-quality pitfall. The remaining gap is date-format/optionality detail for desde and ate.

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 0%, so the description must carry parameter meaning. It explains ignorar_categorias substantively (what to pass and why) and implies desde/ate define the period, but gives no format for the date strings and does not indicate that ate is optional/open-ended.

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?

States a specific operation (sum of DEBIT outflows) with explicit grouping dimensions (category and currency), a time scope (period), and an output ordering (largest to smallest). This clearly separates it from siblings like transacoes (raw listing), saldo (balance) and faturas (invoices).

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?

The second sentence gives real guidance on how to use ignorar_categorias and why (avoid double-counting internal transfers and invoice payments), which implies the tool's intended use case. However, it never says when to pick this over transacoes or faturas, and no exclusions or alternatives are named.

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