Skip to main content
Glama
invoices-mcp

invoices-mcp

by lucasoishi

Monthly totals

monthly_totals
Read-onlyIdempotent

Calculate monthly spending and credits from bank invoices, filtered by bank or category, to compare calendar-month totals in BRL.

Instructions

Spend and credits per calendar month, optionally for one bank or category. Months come from transaction dates. Amounts are in BRL. A positive amount is money leaving the account or card (a purchase or fee); refunds, card payments and deposits are reported separately as credits.

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": "monthly_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoOnly this bank: nubank, itau. Omit to include every bank.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds substantive semantics beyond the annotations: months are derived from transaction dates, amounts are in BRL, and a positive amount means money leaving the account while refunds/payments/deposits appear separately as credits. That sign convention is a real behavioral detail an agent could not otherwise infer.

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?

Four short sentences, each carrying distinct information; the core output semantics (what is counted and how it is signed) are front-loaded before the secondary currency and credit notes.

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

Completeness5/5

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

With no output schema, the description carries the burden of explaining returns, and it does: it defines the two reported quantities, the currency, the sign convention, and where credits land. For a two-optional-param aggregation tool, nothing essential is missing.

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%: bank is fully documented with its enum in the schema, while category has no description in either place. The description clarifies that these are optional scoping filters ('optionally for one bank or category'), but does not explain how category matches or how multiple values combine, so it only partially compensates for the gap.

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 names the resource (spend and credits) and its grouping (per calendar month), which is specific enough to distinguish it from a raw listing. It does not explicitly contrast with the closest siblings such as spending_summary or compare_months, so an agent must infer the boundary.

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?

It states that bank and category are optional narrowing filters, implying usage, but never says when to choose this over spending_summary or compare_months, nor when it would be inappropriate. Usage is implied rather than guided.

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