Skip to main content
Glama
invoices-mcp

invoices-mcp

by lucasoishi

List invoices

list_invoices
Read-onlyIdempotent

Retrieve parsed bank invoice files with bank, month, card/account type, due date, transaction count, and spend; see skipped files and whether parsed lines match statement totals.

Instructions

List the invoice files that were found: bank, month, type (card or account), due date, transaction count and spend. Where a statement prints its own total, check says whether the parsed lines add up to it. Files that could not be read are listed under skippedFiles. 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": "list_invoices"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare this is a safe, idempotent, read-only, closed-world operation, yet the description adds substantial non-obvious behavior: the `check` reconciliation flag, the skippedFiles bucket for unreadable files, BRL currency, and the sign convention that positive amounts are debits while refunds/payments/deposits are credits. These semantics are exactly what an agent needs to interpret results and cannot be inferred from the annotations.

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?

Three dense sentences, front-loaded with the core purpose, with no filler or redundancy. It is information-rich rather than bloated, though the sign-convention sentence is long and could be split for scannability.

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?

With no output schema, the description correctly takes on responsibility for return-value semantics (fields, currency, credits vs debits, skippedFiles) and does so well. It omits the optional bank filter and any notion of ordering, pagination, or result size, which leaves a small gap for a listing tool.

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 description coverage is 100% and the single `bank` enum parameter is fully documented by the schema itself. The description mentions 'bank' only as a returned attribute and never explains the filtering behavior, so it adds nothing over the schema. Baseline 3 is appropriate when the schema carries the load.

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 clear verb+resource ('List the invoice files') and enumerates exactly what each entry contains (bank, month, type, due date, transaction count, spend), which is specific enough to separate it from siblings like spending_summary or monthly_totals. It stops short of naming an alternative, so it doesn't quite reach the 5 level.

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 explicit when-to-use or when-not-to-use guidance. Nothing tells the agent why it would call list_invoices rather than search_transactions or monthly_totals, and no preconditions or exclusions are stated. Usage is only inferable from the returned fields.

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