homebox-mcp

Overview Schema Source Related Servers Discussions Admin

move_item

Idempotent

Move an item into a location or container item by name, path, or asset ID; a partial PATCH keeps all other fields unchanged.

Instructions

Move an item into a location or into another item (assetId / alias field / exact name).

location is the destination's name or /-separated path — a location (see list_locations) or a container item, e.g. a lens into 'Camera Bag' or 'Office/Camera Bag' — or a container item's assetId ('000-012'). A location wins over an item with the same name; reach the item with a longer path or its assetId. A name that matches more than one location, or more than one item, is refused. Uses a partial PATCH, so nothing else on the item changes.

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>",
      "location": "<location>"
    },
    "name": "move_item"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes
`identifier`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations only declare idempotentHint, so the description carries most of the behavioral burden, and it does add real context: 'Uses a partial PATCH, so nothing else on the item changes' and the statement that ambiguous name matches are refused. It still says nothing about required permissions or what is returned on success.

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?

It is a compact block, front-loaded with the core action, then the destination semantics, then the non-destructiveness note. The parenthetical at the top is slightly ambiguous about which parameter its forms apply to, but there is no filler.

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 two-parameter mutation tool with minimal annotations and no output schema, the description covers resolution rules, ambiguity errors, and mutation scope. Missing are the return value and any permission or reversibility notes, which keeps it short of full completeness.

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?

Schema description coverage is 0%, so the description must compensate, and it does for 'location': it explains accepted forms (name, /-separated path, container assetId) and the tie-breaking rule. The forms 'assetId / alias field / exact name' in the first sentence are presumably meant to tell you what 'identifier' accepts, but they are not tied explicitly to the parameter, leaving that half less clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Move') and resource ('an item') and explains the two target kinds: a location or a container item. It is clear what the tool does, but it never distinguishes itself from the sibling tool 'set_location', which an agent could reasonably confuse with it.

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 concrete guidance on constructing the destination, including resolution precedence ('A location wins over an item with the same name') and the workaround ('reach the item with a longer path or its assetId'). It gives no explicit when-to-use/when-not comparison against 'set_location', so the usage guidance is strong but incomplete.

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