Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Update item

update_item

Change fields on an existing life-admin item, leaving omitted fields unchanged; clear selected fields or append a dated history note. Use mark_handled for completed renewals so due dates advance.

Instructions

Change fields on an existing item; anything you leave out stays as it is. clear removes a field. add_note appends a dated line to the item's history. For a renewal or payment that has been dealt with, use mark_handled instead so the due date moves on.

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

Input Schema

NameRequiredDescriptionDefault
dueNoNext renewal, payment or expiry date as YYYY-MM-DD. Only a date the user gave you.
refNoPolicy, account or order reference; only the last four are kept
costNoCost per period as the user stated it (for income: the amount received). Never estimate.
itemYesThe item's current title
tagsNoA few lowercase tags, e.g. ['car']
typeNo
clearNoFields to remove
titleNoNew title
periodNoHow often it repeats (default one-off)
add_noteNoAppend a dated line to the history
currencyNoThree-letter code, default GBP
providerNoWho it is with, e.g. 'Octopus Energy'
auto_renewsNoTrue if it renews or charges automatically unless stopped
remind_daysNoDays before due to start reminding (default 14)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior1/5

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

Annotations declare destructiveHint=false, but the description says `clear` removes a field, which is a destructive update/removal of stored data. This directly conflicts with the annotation, triggering an annotation contradiction despite otherwise useful disclosure of partial-update and add_note behavior.

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?

The description is short and front-loaded, with no wasted wording. The partial-update rule, clear/add_note behavior, and sibling alternative are each stated once.

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 14-parameter update tool with no output schema and high schema coverage, the key mutation semantics are covered. It omits return-value behavior and does not explicitly explain item identification, but those gaps are minor given the schema detail.

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?

Schema description coverage is already 93%, so the baseline is 3. The description adds cross-parameter meaning: omitted optional fields stay unchanged, and `clear` explicitly removes values, which helps interpret the 14-param partial-update schema.

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 states a specific verb and resource: 'Change fields on an existing item.' It immediately clarifies partial-update semantics and distinguishes the tool from mark_handled for already-handled renewals or payments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes an important alternative case: for a renewal or payment that has been dealt with, use mark_handled instead. It does not discuss add_item or delete_item, though 'existing item' and 'change fields' imply their exclusion.

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