Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Despesas recorrentes do mês

list_recurring_expenses
Read-onlyIdempotent

Retrieve active recurring expenses for a specified month, including rule, frequency, amount, and occurrence details to review scheduled financial commitments.

Instructions

Lista as despesas recorrentes ativas em um mês, com regra, frequência, valor e ocorrências.

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

Input Schema

NameRequiredDescriptionDefault
periodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the meaningful behavioral detail that only active recurring expenses are returned and which fields come back, but says nothing about ordering, pagination, or what happens for a month with no occurrences.

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?

A single front-loaded sentence with no filler; the scope and returned fields are packed efficiently. It is arguably too terse for the amount of guidance an agent needs, but nothing is wasted.

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?

For a simple one-parameter read-only list tool with rich annotations and no output schema, the description covers purpose, filter, and returned fields adequately. The remaining gap is the period format, which the schema pattern covers implicitly.

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?

There is one parameter with 0% schema description coverage; the schema only supplies a regex pattern. The description compensates partially by indicating the parameter is a month ('em um mês'), but it never states the expected YYYY-MM format or timezone/period boundary semantics, so an agent must read the regex to call it correctly.

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 ('Lista as despesas recorrentes') plus a scope ('ativas em um mês') and the fields returned (regra, frequência, valor, ocorrências). This distinguishes it reasonably from siblings like list_bills or list_installments, though it never names an alternative explicitly.

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 is only implied: the 'ativas' qualifier hints that inactive recurring expenses are excluded, and 'em um mês' implies a monthly scope. There is no explicit when-to-use guidance, no statement of when to prefer list_bills or list_installments, and no prerequisites mentioned.

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