Skip to main content
Glama
dgahagan

homebox-mcp

by dgahagan

set_item

Idempotent

Update a Homebox item's name, description, notes, quantity, purchase details, flags, or custom fields in one call, changing only the values you specify.

Instructions

General item editor (assetId / alias field / exact name): rename, edit description/notes/quantity, purchase info, insured/archived flags, and custom fields in one call.

Only the args you pass are changed. Quantity-only changes go via a partial PATCH; anything else uses a full-body PUT that preserves the rest of the item (the 0.26 PUT-clears gotcha). fields maps custom-field name -> value, typed by JSON type (see set_fields). To move an item use move_item; for warranty/identity/tags see set_warranty/set_identity/set_tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
fieldsNo
insuredNo
archivedNo
new_nameNo
quantityNo
identifierYes
descriptionNo
purchase_dateNo
purchase_fromNo
purchase_priceNo
Behavior5/5

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

The only annotation is idempotentHint. The description goes far beyond that by disclosing partial-update semantics ('Only the args you pass are changed'), the quantity-only PATCH vs full-body PUT distinction, the '0.26 PUT-clears gotcha', and how custom-field values are typed. This is rich, behavior-relevant context.

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?

Three sentences: purpose, behavior, and sibling pointers. Each sentence earns its place, front-loaded with the primary capability and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, no schema descriptions, and no output schema, this description covers purpose, identifier forms, update behavior, custom-field mapping, and sibling tools. The only minor gaps (date format, currency units) are easily inferable and do not hamper correct usage.

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 0%, so the description must compensate. It does clarify identifier resolution (assetId/alias/exact name) and the `fields` map semantics. However, it stops short of detailing formats for purchase_date/purchase_price, leaving some parameters to be inferred purely from their names.

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?

Description opens with 'General item editor' and lists concrete capabilities (rename, edit description/notes/quantity, purchase info, insured/archived flags, custom fields). It also identifies the identifier forms (assetId / alias / exact name) and differentiates from sibling tools by referencing move_item and set_warranty/set_identity/set_tags.

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?

Explicitly states which sibling tool to use for other concerns ('To move an item use move_item; for warranty/identity/tags see set_warranty/set_identity/set_tags'). Also explains when PATCH vs PUT is used, giving clear context for behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dgahagan/homebox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server