Skip to main content
Glama

add_household_items

Add belongings (furniture, clothing, jewelry, tools, collections, household goods) to the estate's one "Household and personal items" list — several per call. Use this, NOT create_asset, for personal belongings: each is a row of that list, not its own asset, and the list has one short task set. An item worth more than $5,000, a firearm, or a titled vehicle/boat is moved to its own asset automatically (the result says which). Value and recipient are optional; record a recipient only when the customer named who gets it. Adds rows to the estate's Household and personal items list. An item over $5,000, a firearm or a titled vehicle becomes its own asset instead; for eligible paid estates a new list or separate asset may start task preparation. Repeating within a few minutes adds nothing.

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>",
      "items": "<items>"
    },
    "name": "add_household_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesThe belongings, e.g. [{"name":"Mink coat","value":300},{"name":"Jewelry","value":800},{"name":"Two desks","value":50}].
estate_idYesThe estate to act on. Call list_my_estates first to get this id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the bar is lower; the description still adds real behavior — automatic promotion of high-value/firearm/titled items to their own asset, the side effect of starting task preparation for eligible paid estates, and a short-window dedupe ("repeating within a few minutes adds nothing"). The dedupe statement sits in mild tension with idempotentHint=false, but it is a time-boxed dedupe rather than a claim of true idempotency, so it reads as clarifying rather than contradictory.

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 key routing rule is front-loaded and clear, but the text repeats itself: the $5,000/firearm/titled-vehicle rule is stated twice in near-identical wording, and "Adds rows to the estate's Household and personal items list" restates the opening sentence. Roughly a third of the text is redundant.

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?

There is no output schema, and the description covers the important edge cases an agent needs (auto-promotion to asset, task-preparation side effect, dedupe window) and notes that the result reports which items were moved. Return shape is only gestured at ("the result says which"), which is the one remaining gap for a write tool.

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% with only two parameters, so the schema carries most of the load; the description adds useful framing (multiple items per call, optional value/recipient) but does not clarify the item structure, which the schema itself renders ambiguously as strings versus an example of objects. Baseline 3 is appropriate.

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 — adding personal belongings as rows of the estate's single "Household and personal items" list, several per call — and explicitly distinguishes it from create_asset. An agent can tell immediately which tool owns personal property versus standalone assets.

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

Usage Guidelines5/5

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

Gives a direct routing rule ("Use this, NOT create_asset, for personal belongings") plus the boundary conditions that override it: items over $5,000, firearms, and titled vehicles/boats become their own asset. It also tells the agent that value and recipient are optional and that a recipient should only be recorded when the customer named one.

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