Skip to main content
Glama

Month summary

get_month_summary
Read-onlyIdempotent

Income, expenses and balance of a month (personal, self-employed and total) and the top expense and income categories. Past and current months count real transactions; future months, forecast ones. Transfers between accounts are not income or expense.

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

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
monthNoYYYY-MM (default: current month).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real semantic context beyond them: future months return forecast data instead of actuals, and inter-account transfers are excluded from income and expense totals — both material to interpreting results correctly.

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?

Three dense sentences, front-loaded with what is returned, followed by the temporal semantics and the transfer exclusion. Every sentence carries information an agent needs; nothing is padding.

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?

With no output schema, the description usefully sketches the return content (income, expenses, balance across personal/self-employed/total, plus top categories). Minor gaps remain, such as currency or whether category counts are limited, but the essential behavior is covered for a two-optional-parameter read tool.

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?

Schema coverage is 100%, so book and month are fully documented in the schema itself, making 3 the baseline. The description adds only indirect meaning to the month parameter by explaining how past, current, and future months are treated; it gives no additional syntax or format guidance.

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 specific resource (a month's income, expenses, balance) and the breakdown it returns (top expense and income categories), which is more than a restatement of the title. It does not explicitly name a sibling it is not, but the forecast-versus-real distinction implicitly separates it from get_forecast.

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 implied rather than stated: the past/current-versus-future sentence tells an agent which data it will get for a given month, which helps selection. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as get_forecast for forward-looking questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources