Skip to main content
Glama
Tafeen

Homebox MCP Server

by Tafeen

add_product

Add a product or subitem to your Homebox inventory with options for location, parent item, identifiers, purchase details, metadata, and status.

Instructions

Add a new product (or subitem) to Homebox with grouped parameters.

    Args:
        identity: Required product identity {"name": str, "description": str, "asset_id": str}
        location: Optional location {"id": str} or {"name": str}
        parent_item: Optional parent item {"id": str} or {"name": str}.
            If provided, the new item is created as a subitem and parent_item
            takes precedence over location.
        identifiers: Optional manufacturing info {"serial_number", "model_number", "manufacturer"}
        purchase: Optional purchase details {"price": float, "seller": str, "date": str, "warranty_expires": str}
        metadata: Optional extra info {"notes": str, "quantity": int, "tag_ids": [str], "tag_names": [str], "custom_fields": [{}]}
        status: Optional flags {"archived": bool, "insured": bool, "lifetime_warranty": bool}

    Behavior:
        - Standalone product: provide a location (id or name).
        - Subitem product: provide parent_item (id or name).
        - If both parent_item and location are provided, parent_item wins.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
identityYes
locationNo
metadataNo
purchaseNo
identifiersNo
parent_itemNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description should fully disclose side effects. It explains the grouping and precedence well, but does not mention what happens on success or failure (e.g., return value, error conditions). This leaves some behavioral gaps.

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 well-structured with an Args list and Behavior section, front-loading the purpose. It is somewhat lengthy but every part adds value; minor redundancy could be trimmed.

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 the complexity (7 params, nested objects) and lack of annotations, the description covers the core functionality and parameter semantics well. The presence of an output schema reduces the need to describe return values, but error handling is not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description provides detailed structured Args documentation for all 7 parameters, including expected keys and optionality. This fully compensates for the schema's lack of semantic detail.

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 ('Add') and resource ('product or subitem' to Homebox). It distinguishes from the sibling 'add_bulk_products' by focusing on single product addition and explains standalone vs subitem scenarios.

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 behavior section explicitly explains when to use location vs parent_item, including the precedence rule. However, it does not explicitly mention alternatives like 'add_bulk_products' for batch operations or conditions to avoid using this tool.

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/Tafeen/homebox-mcp'

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