Skip to main content
Glama
Supermaxman

Homebox MCP Server

by Supermaxman

create_item

Add a new item to your Homebox inventory with details like name, location, quantity, and serial number.

Instructions

Create a new inventory item in Homebox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesItem name (max 255 characters)
descriptionNoItem description (max 1000 characters)
locationIdNoLocation ID (UUID) where the item is stored
parentIdNoParent item ID (UUID) if this item belongs to another item (e.g., item in a box)
labelIdsNoArray of label IDs (UUIDs) to associate with the item
quantityNoQuantity of the item (default: 1)
serialNumberNoSerial number of the item (max 255 characters)
modelNumberNoModel number of the item (max 255 characters)
manufacturerNoManufacturer of the item (max 255 characters)
notesNoAdditional notes about the item (max 1000 characters)
purchasePriceNoPurchase price of the item
soldPriceNoSold price of the item
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Create a new inventory item' but omits details like required permissions, side effects (e.g., automatic assignment of IDs), or what happens upon creation (e.g., response format). This is insufficient for an agent to understand the tool's behavior.

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

Conciseness4/5

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

The description is a single, concise sentence of six words. It is appropriately brief and to the point, with no wasted words. However, it could be expanded slightly to improve clarity without losing conciseness.

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

Completeness2/5

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

Given the tool has 12 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, required fields beyond 'name', or potential errors. For a complex creation tool, this leaves significant gaps for an agent.

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?

The input schema has 100% description coverage, so the schema already explains each parameter's meaning. The tool description adds no additional semantic value beyond what the schema provides. Per guidelines, 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?

The description clearly states the action ('Create') and the resource ('a new inventory item in Homebox'). The name 'create_item' reinforces this. It distinctly identifies the tool's primary function, distinguishing it from sibling tools like 'add_item_attachment' or 'update_item'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites, limitations, or context such as when to use 'add_item_attachment' for attachments or 'update_item' for modifications. Agents have no basis for choosing this tool over others.

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/Supermaxman/Homebox-MCP-Server'

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