Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Add spending

add_spending

Record a payment or refund and categorize it to track spending, income, and refunds in local life-admin files.

Instructions

Record one payment or refund the person tells you about ("I spent £42 on a meal out"). The category is worked out from the description unless given. Amounts are always positive; set money_in for refunds or money received. Categories: bills (Bills & energy), groceries (Groceries), shopping (Shopping), going-out (Eating & going out), transport (Transport), tax (Tax), subscriptions (Subscriptions), savings (Savings), income (Income), transfers (Transfers), other (Other).

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": {
      "amount": "<amount>",
      "description": "<description>"
    },
    "name": "add_spending"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (default today)
amountYesAmount in pounds, e.g. 42.50
categoryNo
money_inNoTrue for a refund or money received
descriptionYesWhat or where, e.g. 'Meal out at The Red Lion'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent write. The description adds meaningful context beyond that: the category is auto-derived from the description unless supplied, amounts are always positive, and money_in must be set for refunds or received money. That is exactly the kind of behavioral detail annotations cannot express.

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 definition is front-loaded with the core action and an illustrative example before moving into semantics and the category list. The category enumeration is long but earns its space because it maps opaque enum keys to labels; nothing is redundant.

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?

For a five-parameter mutation tool with no output schema and partial annotation coverage, the description covers the key behaviors: singular recording, auto-categorisation, positive amounts, and refund handling. It stops short of describing failure modes or validation (e.g. the 1,000,000 cap or duplicate handling), but nothing essential to a correct call is missing.

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?

With schema coverage at 80%, the baseline is 3, but the description adds real value: it explains that money_in means refunds or received money and expands each enum key into a human-readable label (e.g. going-out = 'Eating & going out'). The only gap is that date and description parameters are not elaborated on in the prose.

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 opens with a specific verb and resource: 'Record one payment or refund the person tells you about', backed by a concrete example. It is immediately clear what the tool does, though it never names or contrasts itself with siblings such as add_item or categorise, so an agent must infer the boundary.

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 by 'the person tells you about' and by the refund/money-received case, but there is no explicit when-to-use versus when-to-pick-an-alternative guidance. An agent knows the scenario but not the exclusions or handoffs to sibling tools.

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