Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Update rainy-day pot

update_pot

Record and adjust rainy-day pot savings by setting the saved amount, adding or withdrawing funds, or setting a savings goal using only figures you provide.

Instructions

Record what is in the rainy-day pot: set the amount saved, add to it (or take from it with a negative amount), or set a goal. Only use figures the person gave you.

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

Input Schema

NameRequiredDescriptionDefault
addNoAdd this much (negative to take some out)
savedNoSet the amount saved so far
targetNoGoal amount (0 clears it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish non-readonly, non-destructive, non-idempotent, closed-world behavior. The description adds genuine context beyond that: a negative amount withdraws, target 0 clears the goal, and values must come from the user rather than being invented — a real safety constraint not captured by any annotation. It stops short of saying what a combined set-plus-add call does or what the mutation returns.

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?

A single sentence that front-loads the resource and enumerates the modes in the order an agent would choose them, followed by a short constraint clause. Nothing is padding and nothing needed is buried.

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 zero required parameters and no output schema, the description covers all three operating modes and the sourcing constraint, which is close to sufficient for a three-optional-param mutation. It leaves one real gap: it never says whether saved, add, and target may be combined in a single call or which wins, and it does not indicate the result of the write.

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%, and each parameter already carries its own description including the negative-amount and zero-clears semantics. The description restates these in prose but adds no format, unit, currency, or interaction rules beyond what the schema provides, so baseline 3 applies.

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?

Names a specific verb (record/update) and resource (rainy-day pot) and enumerates the three operations it performs: set saved, add/take from, or set a goal. An agent can distinguish this from read-oriented siblings like rainy_day_plan or get_stats without opening the schema.

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 line "Only use figures the person gave you" is a grounding constraint, not when-to-use guidance; it tells the agent how to source values but not when this tool is preferred over rainy_day_plan, add_spending, or money_ahead. Usage is implied by the enumeration of operations rather than stated as selection criteria.

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