Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Mark handled

mark_handled

Record when a recurring or one-off bill, renewal, or subscription is paid, renewed, switched, or replaced; log it in history and advance or clear the due date, including cost changes.

Instructions

Record that the user has dealt with an item (renewed, paid, switched, replaced). Logs it in the item's history and moves the due date on: repeating items roll forward by their period (keeping month-end dates right), next_due sets a date explicitly, and a one-off item's due date is cleared. Pass new_cost when the price changed; the old and new prices are logged.

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": {
      "item": "<item>"
    },
    "name": "mark_handled"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe item's title
noteNoWhat was done, e.g. 'Renewed with Admiral after haggling'
new_costNoThe new cost per period, if it changed
next_dueNoSet the next due date explicitly (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations: annotations only say non-read-only, non-idempotent, non-destructive, while the description explains exactly what is mutated — history entry appended, repeating items rolled forward by their period with month-end handling preserved, one-off items' due dates cleared, and old/new prices logged. It doesn't state what happens if the item title doesn't match or what the call returns, so it falls short of full disclosure.

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?

Front-loaded with 'Record that the user has dealt with an item', then the effects, then the parameter-conditioned behaviors. One long sentence chains a lot together, but every clause carries a distinct fact and nothing is repeated.

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 four-parameter mutation with no output schema, the description covers what is changed and how the due date is decided in every branch, which is the hard part. The only gap is the response: an agent isn't told whether the new due date is returned or must be fetched with get_item.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: `next_due` is presented as overriding the default roll-forward behavior, and `new_cost` is framed as a conditional flag that also writes both old and new prices to the log. That interaction between parameters and resulting behavior is not derivable from the schema alone.

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?

States a specific verb and resource — 'Record that the user has dealt with an item' — and enumerates the real-world events it covers (renewed, paid, switched, replaced). It also distinguishes itself from a generic edit by describing the side effects (history log, due-date roll-forward), so an agent can tell it apart from update_item.

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 opening clause implies when to use it: the user has already handled the item. It also gives conditional guidance ('Pass `new_cost` when the price changed'; `next_due` for an explicit date). But it never says when not to use it or names an alternative such as update_item for editing an item without recording completion.

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