Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Histórico de faturas do cartão

get_invoice_history
Read-onlyIdempotent

Retrieve a card's invoice history with totals and payment status per period to review past billing and payment records.

Instructions

Retorna o histórico de faturas de um cartão, com totais e situação de pagamento por período.

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_invoice_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID do cartão.
periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds value beyond that by stating what the response contains (totals and payment status per period), which matters because there is no output schema. It does not cover history depth, pagination, or how many periods are returned.

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?

The description is a single front-loaded sentence with no filler, and it immediately names the resource and the returned content. It could be slightly richer without becoming verbose.

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 complete annotations, the description covers purpose and return content adequately. It leaves the period parameter's format and the history's scope or time limits unaddressed, which an agent would need to know to call the tool correctly.

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?

Only half the parameters are documented in the schema: id has a description, but period has no explanation of its YYYY-MM pattern. The description links period to per-period invoice grouping, which adds slight meaning, but it does not explain the format or whether the parameter is optional.

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 states a specific verb and resource: it returns a card's invoice history with totals and payment status per period. An agent can identify what data comes back, but nothing distinguishes this tool from siblings such as get_card or add_invoice_payment.

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 guidance on when to use this tool versus alternatives, nor any prerequisites such as authentication or whether the card must exist. The phrase 'por período' only hints that results can be scoped by period, without saying whether that is required or optional.

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