Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Rainy-day plan

rainy_day_plan
Read-onlyIdempotent

Calculate how much you can save each month from your own income and spending records. Smooth yearly bills into set-asides and get risk-checked options with time to savings goals.

Instructions

Work out how much the person could put aside, from their own income items and spending records: big yearly bills smoothed into monthly set-asides, then Gentle, Steady and Stretch options, each with a risk check against their tightest recent month and time to a £1,000 pot and to three months of essentials. Flags varying income, rising spending, big bills due soon and signs of borrowing. Arithmetic only: never recommend financial products, accounts or investments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description does not need to cover safety. It adds real behavioral context instead: the computation smooths large annual bills into monthly set-asides, runs a risk check against the tightest recent month, and raises specific flags for varying income, rising spending, big bills due soon and borrowing. The explicit scope limit (arithmetic only, never recommend financial products or investments) is a meaningful guardrail. It stops short of saying what happens when data is missing or sparse.

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 description is dense but front-loaded: it leads with the core computation and then enumerates the output shape and the guardrail. The long middle clause listing options, risk check and timelines is heavy but each element carries information. No filler sentences.

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 parameters and no output schema, the description carries the burden of describing results in prose, and it does so: three plan tiers, a risk check, timelines to two savings targets, and four flag categories. The only omission is edge-case behavior when records are absent or income is zero, which matters for a computation tool.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing further to document. The description does clarify the implicit inputs it draws on (the user's own income items and spending records), which is a modest bonus beyond a bare no-arg signature.

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 opens with a specific verb-plus-resource: work out how much the person could put aside from their own income items and spending records. It then names the concrete outputs (smoothed yearly bills, Gentle/Steady/Stretch options, timeline to a £1,000 pot and three months of essentials), which distinguishes it clearly from siblings such as spending_summary 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 implied rather than stated: an agent can infer this is the tool for building a savings plan, and the closing line rules out product recommendations. However, there is no explicit routing such as when to use this instead of money_ahead or spending_summary, and no statement of prerequisites (e.g. that income items and spending records must already exist).

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