Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Money ahead

money_ahead
Read-onlyIdempotent

Calculate payments due before next payday, total them, and estimate what remains from a given balance; ask for the balance if unknown.

Instructions

Payments due between today and the next payday (from income items, moved to the working day before if payday falls on a weekend or bank holiday), with their total. Given the person's current balance, says roughly what is left until payday. Never guess the balance: ask for it.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook this many days ahead instead of to payday
balanceNoCurrent bank balance the person gave you

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the description is not required to restate that. It adds real behavior instead: payments roll back to the working day before if payday lands on a weekend or bank holiday, the remaining figure is approximate ('roughly'), and the balance must never be fabricated. It stops short of saying what the response contains when no balance is supplied.

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?

Three sentences, front-loaded with the scope and the rollback rule before the balance caveat. The nested parenthetical about weekends and bank holidays is dense but carries necessary information, and the closing imperative is short and memorable.

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 nested objects and no output schema, the description covers what an agent needs: the window, that a total is returned, the approximate remainder, and the rule against inventing a balance. The one gap is the behavior when balance is omitted, which is only implied.

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 both parameters are already documented, making the baseline 3. The description adds a little beyond the schema by framing 'balance' as something the person must supply rather than an inferred value, but it does not clarify how the 'days' override interacts with the payday window.

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 and a precise time window: payments due between today and the next payday, with their total, plus an estimate of what is left. That window definition implicitly separates it from a generic 'due soon' view, but no sibling tool is named, so an agent must infer the boundary itself.

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 payday-bounded scope, and there is one explicit directive: 'Never guess the balance: ask for it.' There is no statement of when to prefer this over alternatives such as due_soon, nor any exclusion, so the agent gets a nudge but not a routing rule.

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