Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Spending summary

spending_summary
Read-onlyIdempotent

Summarize weekly or monthly spending by category, compare it with your usual average, and see money in, savings, and top shops.

Instructions

What was spent this week or month by category, compared with what's usual for the person (the average of up to four earlier periods), plus money in, money saved and the biggest shops. Weeks run Monday to Sunday. offset 1 means last week/month.

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

Input Schema

NameRequiredDescriptionDefault
offsetNo0 = this one (default), 1 = the previous one
periodNoDefault week

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: what 'usual' means (average of up to four earlier periods), that weeks run Monday to Sunday, and what the response covers. It does not state how much history is required before a baseline exists, which is the main remaining ambiguity.

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?

The purpose and payload are front-loaded in the first sentence, followed by two short boundary clarifications. It is dense and slightly run-on, but every sentence carries information and 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?

With only two optional parameters, no output schema, and full annotation coverage, the description does the necessary work of explaining what comes back and how the comparison is computed. A minor gap remains around data availability for the four-period baseline over month lengths and offset 24 limits.

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 description coverage is 100%, and both parameters are already documented in the schema, including the offset default and the period default. The description's 'offset 1 means last week/month' largely restates the schema rather than extending it, though tying offset to the week/month period pairing is a mild clarification. Baseline 3 is appropriate.

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 a specific resource (spending this week/month by category) and enumerates the payload contents: category totals, a baseline comparison, money in, money saved, and biggest shops. It is clearly a retrospective aggregate rather than a mutation, but it does not contrast itself with plausible siblings such as get_stats or money_ahead.

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 through the described scope (this week or this month, by category, versus a personal baseline) and the note that offset 1 means the previous period. There is no explicit statement of when to prefer this over get_stats or money_ahead, and no when-not guidance.

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