homebox-mcp

Overview Schema Source Related Servers Discussions Admin

duplicate_item

Duplicate an existing home inventory item to create a new copy, optionally carrying over custom fields, attachments, and maintenance records. Use when you buy a second version of the same item.

Instructions

Duplicate an existing item (assetId / alias field / exact name), e.g. "I bought a second one". prefix is prepended to the new item's name. Copies custom fields by default; attachments and maintenance log only on request. NOTE: copied custom fields include the alias field verbatim — if you use one, give the copy its own value via set_fields right after. Returns the new item's id and assetId.

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": {
      "identifier": "<identifier>"
    },
    "name": "duplicate_item"
  }
}

Input Schema

Name	Required	Default
`prefix`	No	Copy of
`identifier`	Yes
`copy_attachments`	No
`copy_maintenance`	No
`copy_custom_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries full burden for behavioral disclosure. It covers defaults for copying custom fields/attachments/maintenance, the prefix behavior, a non-obvious alias-field caveat, and return values (id and assetId). This is rich, useful context beyond the schema.

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

Conciseness5/5

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

The description is front-loaded with the main action, then efficiently details defaults, caveats, and return values. Each sentence earns its place with no fluff or repetition of schema field names.

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 5 parameters, no annotations, and no output schema, the description provides all essential context: default behavior, the alias pitfall, how to correct it, and what the tool returns. It is complete for an agent to select and invoke the tool 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?

Schema description coverage is 0%, so the description must explain all params. It explains 'identifier' (assetId / alias / exact name), 'prefix' (prepended to name), and the three boolean copy flags with their defaults. Every parameter's semantics are effectively described.

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 opens with a specific verb-resource pair ('Duplicate an existing item') and clarifies the identifier forms (assetId / alias field / exact name), immediately distinguishing it from sibling tools like create_item or set_item. The example use case ('I bought a second one') further reinforces the intended purpose.

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 gives a clear use case via the example and explains when to use the tool (duplicating an item with copy behavior). It does not explicitly name alternatives or exclusion conditions, but with no annotations and a clear context, the guidance is sufficient for selection.

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