Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Listar faturas do período

list_invoices
Read-onlyIdempotent

Retrieve invoices for all cards in a given month, including totals, closing/due dates, payments, adjustments, and per-person splits; choose compact or full detail.

Instructions

Lista as faturas de todos os cartões em um mês: total, fechamento, vencimento, pagamentos, ajustes e rateio por pessoa. Os itens vêm em versão compacta por padrão; use detail: "full" para o objeto completo.

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": {
      "period": "<period>"
    },
    "name": "list_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNocompact devolve os itens essenciais; full devolve o objeto completo da API.compact
periodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds value the annotations do not: it describes the shape of the returned invoice objects and the compact-vs-full default behavior. It omits pagination and any per-card filtering caveats, keeping it short of a 5.

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. Scope and returned fields are front-loaded in the first sentence, and the default-vs-full instruction follows immediately.

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 only two parameters and no output schema, the description does the heavy lifting by enumerating what each invoice contains, which compensates for the missing return schema. The safety profile is already in annotations. Missing pagination/volume behavior and any period format hint are the only notable gaps.

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 50%: `detail` is documented in the schema, while `period` has only a regex pattern with no prose. The description clarifies that `period` means a month ("em um mês") and reiterates the compact/full switch, but adds no format example or guidance on the period pattern.

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 a specific verb and resource ("Lista as faturas") and adds scope ("de todos os cartões em um mês") plus the fields returned (total, fechamento, vencimento, pagamentos, ajustes, rateio). It is clearly distinguishable from siblings like list_bills or list_transactions, though it never explicitly contrasts with them.

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 guidance is limited to the detail switch: compact by default, `detail: "full"` for the complete object. There is no statement of when this tool is the right choice versus alternatives such as list_bills or list_installments, and no exclusions or prerequisites.

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