Dayze — Life Context

Update Inventory Item

update_inventory_item

PATCH semantics — unspecified fields untouched. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	What the user naturally calls the item.
`tags`	No	Replace tags array (sanitized against category mismatches).
`brand`	No
`model`	No
`notes`	No
`status`	No
`subtype`	No	Specific subtype (sweatshirt, jacket, guitar). Alias: item_type.
`category`	No	Broad type: clothing, instruments, electronics, …
`location`	No
`condition`	No
`item_type`	No	Alias for subtype.
`request_id`	No	Client idempotency key (retries return original result).
`inventory_id`	Yes
`serial_number`	No
`purchase_price`	No
`estimated_value`	No
`idempotency_key`	No	Alias for request_id.
`reference_number`	No
`subtype_confidence`	No	0–1 confidence when subtype is uncertain (agent_inferred).

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No	Inventory item record.
`changed`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 4, 2026

changedInput schema / properties / category / description

Previous value: -"Broad type: clothing, shoes, bags, jewelry, …"New value: +"Broad type: clothing, instruments, electronics, …"

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Alias for request_id.",
+  "type": "string"
+}

addedInput schema / properties / request_id

Added value: +{
+  "description": "Client idempotency key (retries return original result).",
+  "type": "string"
+}

changedInput schema / properties / subtype / description

Previous value: -"Specific subtype (sweatshirt, jacket, T-shirt). Alias: item_type."New value: +"Specific subtype (sweatshirt, jacket, guitar). Alias: item_type."

addedInput schema / properties / subtype_confidence

Added value: +{
+  "description": "0–1 confidence when subtype is uncertain (agent_inferred).",
+  "type": "number"
+}

Changed5 schema fields changedSep 4, 2026

addedInput schema / properties / category / description

Added value: +"Broad type: clothing, shoes, bags, jewelry, …"

addedInput schema / properties / item_type

Added value: +{
+  "description": "Alias for subtype.",
+  "type": "string"
+}

addedInput schema / properties / name / description

Added value: +"What the user naturally calls the item."

addedInput schema / properties / subtype

Added value: +{
+  "description": "Specific subtype (sweatshirt, jacket, T-shirt). Alias: item_type.",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Replace tags array (sanitized against category mismatches).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed13 schema fields changedSep 1, 2026
- changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
- addedInput schema / properties / brand
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / condition
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / estimated_value
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / location
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / model
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / notes
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / purchase_price
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / reference_number
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / serial_number
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```
AddedSep 1, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations only indicate the operation is not read-only and not destructive, leaving the description to carry the burden. The description adds meaningful behavior: PATCH semantics, cost per call, and the API-key requirement. It omits edge-case behaviors like not-found responses, but the main mutation risk is clearly disclosed.

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?

A single, front-loaded sentence plus a parenthetical cost/auth note. Every word delivers value, and the key PATCH semantics are stated first. For what it attempts, it is optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter mutation tool with low schema coverage, the description is insufficient. It lacks when-to-use guidance, required-parameter emphasis, alias handling, idempotency behavior, and error cases. The output-schema presence covers return values, but the input-side and usage context remain incomplete.

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

Parameters2/5

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

Schema description coverage is low at 42%, so the description needed to compensate for the many undocumented parameters. It does not: no parameter is mentioned, no aliases such as subtype/item_type or request_id/idempotency_key are explained, and the required inventory_id is not called out. The schema itself provides whatever little parameter meaning exists.

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 conveys PATCH semantics, which implies partial update of an inventory item, and the tool name supplies the resource. It clearly differentiates from add_inventory_item or archive_inventory_item by its update nature, though it does not explicitly name the resource or contrast siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'unspecified fields untouched' provides an important usage contract: this tool is for partial updates rather than a full overwrite. However, there is no explicit guidance about when to choose it over add_inventory_item or other update tools, and no prerequisites such as requiring an existing item.

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

All Dayze — Life Context tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.