Skip to main content
Glama
Tafeen

Homebox MCP Server

by Tafeen

update_maintenance_entry

Update an existing maintenance entry by providing its ID and new values for name, description, cost, or schedule dates.

Instructions

Update an existing maintenance entry.

    Homebox v0.26+ only exposes maintenance entries per-product, so this
    tool requires either `product_id` (preferred) or `product_name` to
    locate the entry's owning entity before issuing the PUT.

    Args:
        entry_id: UUID of the maintenance entry to update (required).
        product_id: UUID of the product/entity owning the entry.
        product_name: Name of the product (used to resolve the entity
            when `product_id` is missing).
        name: New title for the maintenance task.
        description: New detailed description.
        cost: New cost value (numeric).
        scheduled_date: New scheduled date (ISO 8601: YYYY-MM-DD).
        completed_date: New completion date (ISO 8601: YYYY-MM-DD).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNo
nameNo
entry_idYes
product_idNo
descriptionNo
product_nameNo
completed_dateNo
scheduled_dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations set destructiveHint=false and idempotentHint=false, and the description adds that this is an update operation using PUT, requires product ownership info, and returns a dict or error. This adds useful behavioral context beyond the annotations without contradiction.

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 structured with an Args section and a Returns line, front-loading the purpose. However, it is somewhat lengthy, repeating parameter names, which could be more concise.

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 tool's complexity (8 parameters, entity resolution logic), the description covers all needed details: required fields, optional fields with formats, the two-step update process, and return type. With an output schema present, the description is complete enough for an agent to invoke 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?

The input schema has 0% coverage, so the description provides all parameter semantics. It explains the purpose of product_id/product_name for entity resolution, gives format hints for dates (ISO 8601), and describes the cost field. This adds significant meaning missing from the 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 starts with 'Update an existing maintenance entry,' providing a clear verb and resource. It is distinct from sibling tools like 'create_maintenance_entry_for_product' and 'delete_maintenance_entry', making its purpose unambiguous.

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 the need for product_id or product_name to locate the entry due to API constraints, but does not explicitly state when not to use this tool or directly reference alternatives. The context is clear, but explicit exclusions are missing.

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