Skip to main content
Glama
Sign In
Personal Expenses MCP Server

Personal Expenses MCP Server

by gunnaabhinay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_monthly_statement

Retrieve a full breakdown of expenses and the remaining budget balance for a specified month.

Instructions

Returns a full breakdown of all logged expenses and the current remaining budget balance.

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": {
      "name": "<name>",
      "month": "<month>"
    },
    "name": "get_monthly_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
monthYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It clearly states that the tool returns data, implying a read-only operation, but it does not disclose prerequisites (e.g., month initialization) or potential side effects. The description adds context about the returned content but lacks behavioral depth.

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 a single sentence, front-loaded with the verb and key output details. It is concise and free of fluff, making it easy for an agent to parse.

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?

The tool is relatively simple, but the description lacks parameter explanations and prerequisites. An output schema exists, which likely covers the return format, but the description alone is not fully sufficient for confident invocation of the tool.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the 'name' or 'month' parameters. While the parameter names are somewhat self-explanatory, no format, examples, or field meaning are provided. The description fails to compensate for the missing schema documentation.

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 the specific verb 'Returns' and clearly identifies the resource (monthly statement) and its content (full breakdown of logged expenses and remaining budget balance). This distinguishes it from sibling tools like add_person and log_expense by focusing on read-only reporting.

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 implies use for retrieving monthly expense summaries but does not explicitly state when to use it versus alternatives, nor does it mention any exclusions like 'must initialize the month first'. The guidance is implied rather than explicit.

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

Deploy Server

Other Tools