Skip to main content
Glama
dgahagan

homebox-mcp

by dgahagan

create_item

Create a new home inventory item and add details like location, tags, custom fields, and purchase info in one API call.

Instructions

Create an inventory item and enrich it in one call.

location is a location name or /-separated path (must exist; use list_locations). tags are tag names (must already exist; use list_tags). fields maps custom-field name -> value; each value's JSON type picks the field type (string -> text, number -> number [integer-coerced], true/false -> boolean). Returns the new assetId and id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
tagsNo
modelNo
notesNo
fieldsNo
serialNo
locationNo
quantityNo
manufacturerNo
purchase_dateNo
purchase_fromNo
purchase_priceNo
warranty_expiresNo
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the field type coercion behavior (JSON type determines custom field type), the requirement that location/tags must pre-exist, and that the call returns assetId and id. It does not cover failure behavior or atomicity, but the core side effects are clearly described.

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 concise and front-loaded, with the main purpose in the first sentence and supporting details in separate lines. Every sentence adds value; no fluff.

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?

Given 13 parameters, no annotations, and no output schema, the description covers the essential enrichment behavior and return value. It lacks some edge-case details (e.g., how duplicate names are handled), but overall is adequate for an agent to invoke the tool correctly.

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 description coverage is 0%, so the description must compensate. It explains the semantics of location (name or path), tags (must exist), and fields (type mapping), which are the least obvious parameters. However, the other 10 parameters (quantity, dates, etc.) have no additional explanation beyond their schema titles, leaving some ambiguity.

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 states 'Create an inventory item' – a specific verb and resource – and adds 'enrich it in one call' indicating it can also set location, tags, and custom fields at creation. This clearly distinguishes it from sibling update tools like set_item or 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 Guidelines4/5

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

The description provides explicit prerequisites: location must exist (use list_locations) and tags must already exist (use list_tags). This gives clear guidance for using the tool successfully, but does not explicitly discuss when to prefer this over the separate set_* tools.

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