homebox-mcp

Overview Schema Source Related Servers Discussions Admin

set_fields

Idempotent

Update or create custom fields on an existing inventory item by its identifier. Specify field values; existing fields are preserved while new or changed ones are written.

Instructions

Create or update custom fields on an existing item (assetId / alias field / exact name).

fields maps custom-field name -> value; each value's JSON type picks the field type (string -> text, number -> number [integer-coerced — the API 500s on float number values], true/false -> boolean). Upsert semantics: named fields are created or overwritten; other fields are preserved.

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>",
      "fields": "<fields>"
    },
    "name": "set_fields"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	Yes
`identifier`	Yes

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?

The description goes beyond the idempotentHint annotation by explaining field type mapping (string->text, number->number with integer coercion, boolean) and warning about float values causing API 500s. It also clarifies that untouched fields are preserved, providing valuable behavioral context.

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 concise, with the purpose stated in the first sentence and implementation details in the second. Every sentence carries useful information without redundancy.

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?

For a two-parameter tool, the description covers the key behaviors: create/update, type selection, coercion caveat, and preservation of existing fields. The output is not described, but given the absence of an output schema and the nature of a mutation tool, the description is sufficiently complete.

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 no descriptions (0% coverage), so the description fully compensates by explaining the `fields` object mapping and the `identifier` parameter's accepted forms ('assetId / alias field / exact name'). This adds critical meaning 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 'Create or update custom fields on an existing item' with a specific verb and resource. It identifies the tool's scope (custom fields) and the target (existing item), distinguishing it from sibling tools like set_tags or set_item.

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 implies usage for updating custom fields via upsert semantics, but it does not explicitly name alternative tools or state when not to use this tool. Clear context is given, but no exclusions or alternatives are mentioned.

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