Skip to main content
Glama
Sign In

CDF Finance

by io.github.VessellTech
OverviewDiscussionsAdmin

Faturas pendentes

list_pending_invoices
Read-only

Lista as faturas de cartão já fechadas e ainda não totalmente pagas (status CLOSED, OVERDUE ou PARTIAL), ordenadas por data de vencimento crescente. Não inclui faturas OPEN (ciclo ainda em curso, acumulando compras) nem PAID. Use invoice_for_period para o valor da fatura de UM cartão específico (inclusive a que ainda está aberta); use esta tool para o panorama de faturas de cartão pendentes em geral.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds significant behavioral nuance: it includes only CLOSED/OVERDUE/PA RTIAL statuses, excludes OPEN/PA ID, and sorts by due date ascending. This goes well beyond the structured metadata and fully describes the tool's observable behavior.

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?

The description is dense but efficient: it front-loads the core action and object, then clarifies exclusions and closes with a routing hint to a sibling. Every sentence earns its place and there is no fluf.

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?

For a parameterless, read-only list tool with an output schema, the description is complete: it gives statuses, ordering, exclusions, and direct guidance on when to prefer a sibling. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema carries no semantic burden. The description meaningfully explains the tool's scope even though no parameter documentation is needed. This meets the baseline for a parameter-less tool.

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?

The description uses a specific verb ('Lista') with a precise resource: closed credit-card invoices not fully paid, explicitly enumerating statuses (CLOSED, OVERDUE, PARTIAL) and the sort order. It also clearly distinguishes itself from related tools by naming excluded statuses (OPEN, PAID) and the nearby sibling invoice_for_period.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool (general overview of pending card invoices) and when to use an alternative (invoice_for_period for a single specific card invoice, including an open one). It also states what is excluded, so an agent can select correctly without guessing.

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

All CDF Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources