Skip to main content
Glama
MoneyFlow MCP Server

MoneyFlow MCP Server

month_summary

Summarizes a budget cycle's dates, days left, income, actual amounts per original currency, and cash in hand; defaults to the open cycle.

Instructions

One budget cycle: dates, days total and left, income and total actual per currency (original-currency amounts, never folded into one number) and cash in hand (null before the cash cutover). budget_month (YYYY-MM) defaults to the open cycle.

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": "month_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_monthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does so well: it warns that amounts are original-currency and 'never folded into one number,' and that cash in hand is 'null before the cash cutover.' These are exactly the data-semantics traps an agent would otherwise misreport. It stops short of stating read-only status, permissions, or pagination behavior.

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?

It is a single front-loaded sentence that leads with the resource and scope, then lists contents, then the parameter default. It is dense with parentheticals but every clause carries information; nothing is filler.

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?

An output schema exists, so return structure need not be spelled out, and the description correctly focuses on semantics (currency handling, null conditions, default month). For a one-parameter read tool, the only missing piece is guidance on selection versus sibling summary tools.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it gives the format (YYYY-MM) and the default behavior ('defaults to the open cycle') that the bare schema does not convey. The only gap is what happens with an invalid or historical month.

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 the concrete resource ('one budget cycle') and enumerates exactly what the summary contains: dates, days total and left, income, total actual per currency, and cash in hand. An agent can tell this is a month-level financial summary, though it uses a noun phrase with no explicit verb and never distinguishes itself from siblings like category_totals or spending.

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 statement, and no sibling is named as an alternative. The only routing hint is implicit: 'budget_month (YYYY-MM) defaults to the open cycle,' which tells the agent it can omit the parameter but not why to pick this tool over spending or category_totals.

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