Skip to main content
Glama
Tafeen

Homebox MCP Server

by Tafeen

create_maintenance_entry_for_product

Create maintenance records for home inventory items, logging servicing, repairs, or inspections with optional costs and dates. Resolve product by name or use ID.

Instructions

Create a maintenance entry for a specific Homebox product/entity.

    Use this when the user wants to log servicing, repairs, inspections,
    scheduled maintenance, or maintenance cost for an item.

    If only a product name is known, provide `product_name` and this tool
    will resolve the product first, then create the maintenance entry.
    If the product ID is known, provide `product_id` directly for faster execution.

    At least one of `scheduled_date` or `completed_date` must be provided.
    If neither is provided, both default to today's date.

    Args:
        product_id: UUID of the product/entity (preferred if known).
        product_name: Name of the product to search for (used if product_id not provided).
        name: Title/summary of the maintenance task (required).
        description: Detailed description of the work performed or planned.
        cost: Cost of the maintenance in numeric format (e.g., 150.50).
        scheduled_date: Scheduled date for maintenance (ISO 8601: YYYY-MM-DD).
                          Defaults to today if neither date is provided.
        completed_date: Completion date for maintenance (ISO 8601: YYYY-MM-DD).
                          Defaults to today if neither date is provided.

    Returns:
        Created maintenance entry dict on success, or error string on failure.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNo
nameNo
product_idNo
descriptionNo
product_nameNo
completed_dateNo
scheduled_dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations have all false hints, so the description carries the burden. It discloses the write operation (creating an entry) and default date behavior. However, it does not mention potential side effects like overwriting or state changes beyond creation.

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 sections for use cases, parameter details, and return. It is somewhat lengthy but not overly verbose; every sentence contributes to clarity.

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 the complexity (7 parameters, two-way product resolution, date logic), the description covers all essential aspects. It addresses input, defaults, and output format, making it complete for an agent to use correctly.

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?

With 0% schema coverage, the description provides detailed explanations for all 7 parameters, including the logic for resolving product by name vs ID, cost format, and date defaults. This adds significant value beyond the raw schema.

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 it creates a maintenance entry for a Homebox product/entity, listing specific use cases like servicing and repairs. It distinguishes itself from sibling tools such as update_maintenance_entry and delete_maintenance_entry by focusing on creation.

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 explains when to use the tool (logging servicing, repairs, etc.), how to provide product information (name or ID), and date requirements. It does not explicitly state when not to use it or suggest alternatives, but the context is clear.

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