Skip to main content
Glama
MoneyFlow MCP Server

MoneyFlow MCP Server

category_totals

Retrieve signed kept amounts grouped by category, subcategory, and currency for a date range or a budget month. Use it to summarize spending and income totals for budgeting or reporting.

Instructions

Signed kept amount per (category, subcategory, currency), either over [date_from, date_to] (both inclusive) or over one budget month (YYYY-MM), not both.

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

Input Schema

NameRequiredDescriptionDefault
date_toNo
date_fromNo
budget_monthNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / budget_month
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Budget Month"
      +}
    • addedInput schema / properties / date_from / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / date_from / default
      Added value: +null
    • removedInput schema / properties / date_from / type
      Removed value: -"string"
    • addedInput schema / properties / date_to / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / date_to / default
      Added value: +null
    • removedInput schema / properties / date_to / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "date_from",
      -  "date_to"
      -]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose meaningful behavior — the amount is "signed" and "kept" (a filtering/sign convention the agent could not infer) and the two scoping modes are mutually exclusive — but it omits what happens on both/neither being passed, and gives no auth, scope, or result-completeness context.

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?

A single sentence with zero filler; the output shape comes first and the scoping constraint follows. Every clause carries information the agent could not get elsewhere.

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?

An output schema exists, so return values need not be re-explained, and the core semantics are covered. What is missing is the edge-case behavior on argument combinations — all three parameters are optional, yet the text implies exactly one scoping mode must be chosen, leaving the neither/both case undefined.

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 largely does: it explains date_from/date_to as an inclusive range, budget_month as a YYYY-MM value, and the mutual exclusivity between them. It stops short of giving the date_from/date_to string format or stating that exactly one argument is required, given all three default to null.

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 exact output grain — "Signed kept amount per (category, subcategory, currency)" — so an agent knows this is an aggregation, not a listing. It is clear but does not differentiate itself from siblings like month_summary or spending, so an agent still has to guess which aggregate to pick.

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?

The description gives an explicit parameter-level rule: use a date range OR a single budget month, "not both". That is real usage guidance, but it says nothing about when to choose this tool over month_summary or spending, and no indication of what happens when neither parameter is supplied.

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