Skip to main content
Glama

update_household_item

Destructive

Change one row of the Household and personal items list: its name, value or recipient, remove it, or move it to its own asset (track_separately). Item ids come from get_asset_detail on the household list asset or get_estate_summary. Removing only takes it off the list. Edits one row of the Household and personal items list. remove takes it off the list (it is kept as removed, not deleted); track_separately turns it into its own asset, which may start task preparation on eligible paid estates.

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": {
      "estate_id": "<estate_id>",
      "item_id": "<item_id>"
    },
    "name": "update_household_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name.
valueNoNew approximate value in dollars.
removeNotrue to take it off the list (the customer said it's gone, a duplicate, or not the decedent's).
item_idYesID of the household item.
estate_idYesThe estate to act on. Call list_my_estates first to get this id.
recipientNoWho is receiving it (empty string clears).
track_separatelyNotrue to move it to its own asset with its own tasks, when the customer asks (e.g. it needs an appraisal).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real context beyond that: removal is a soft removal ('kept as removed, not deleted') and track_separately creates a new asset that 'may start task preparation on eligible paid estates' — a downstream side effect an agent could not infer from annotations. It omits whether fields not supplied are left unchanged and whether conflicting flags (remove + track_separately) are rejected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping sentence is front-loaded and useful, but the text repeats itself: 'Removing only takes it off the list' is restated as 'remove takes it off the list (it is kept as removed, not deleted)', and 'Change one row...' is restated as 'Edits one row of the Household and personal items list.' Roughly a third of the text is duplication.

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 7-parameter mutation tool with a fully described schema and no output schema, the definition covers the important unknowns: id provenance, soft-removal semantics, and the side effect of converting a row to its own asset. Residual gaps around partial-update behavior and flag conflicts keep it from being complete.

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 every parameter including clear-on-empty recipient and the dollar value is already documented in the schema. The description only reinforces remove and track_separately semantics and supplies id provenance, so baseline 3 is appropriate.

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 opening sentence names a specific verb and resource ('Change one row of the Household and personal items list') and enumerates the mutable fields plus the remove/track_separately operations, which is enough to distinguish it from a general asset-editing sibling. It stops short of explicitly contrasting with update_asset or create_asset, even though 'move it to its own asset' overlaps those tools.

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 gives concrete prerequisites for the required item_id ('Item ids come from get_asset_detail on the household list asset or get_estate_summary') and states the customer conditions that select remove. It does not say when to prefer this over update_asset for non-household assets, so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources