Skip to main content
Glama
Sign In
Homebox MCP Server

Homebox MCP Server

by Tafeen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_maintenance_entry

Destructive

Remove a maintenance entry from Homebox inventory by providing its unique ID. Use to delete records that are no longer needed.

Instructions

Delete a maintenance entry from Homebox.

    Use this to remove maintenance records that are no longer needed.

    Args:
        entry_id: UUID of the maintenance entry to delete (required).

    Returns:
        Success message on success, or error string on failure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "delete_maintenance_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds the return format ('Success message on success, or error string on failure'), which provides behavioral context beyond what annotations offer.

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 concise and well-structured with a short explanation, args section, and returns section. It avoids unnecessary verbosity while covering all essentials.

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?

For a simple delete tool with one required parameter, the description adequately covers purpose, usage, parameter meaning, and return type. The presence of an output schema reduces the need for further detail.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explaining that entry_id is a 'UUID of the maintenance entry to delete (required)', adding meaning beyond the schema's basic type and title.

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 'Delete a maintenance entry from Homebox' with a specific verb and resource. It distinguishes from sibling tools like create_maintenance_entry_for_product, update_maintenance_entry, and list_maintenance_entries.

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 says 'Use this to remove maintenance records that are no longer needed', providing clear context. It doesn't explicitly list exclusions or alternatives, but the use case is straightforward.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools