Dayze — Life Context

Get Inventory Item

get_inventory_item

Read-only

One owned Inventory item in full: specs and spec_template, state with state_freshness (current, recent or stale for each key; check with the user before relying on stale state), capability_summary (one line to plan from, e.g. "Can my computer run this?"), valuations, linked people and photos. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`inventory_id`	Yes	The item id from add_inventory_item, get_inventory or search_inventory.

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No	Inventory item record. With specs: spec_template, specs, state (a timestamped snapshot), state_freshness and capability_summary.
`assets`	No
`people`	No
`valuations`	No
`people_links`	No
`capability_summary`	No	One line to plan from: the item, its stored specs, and its last observed state with its date.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 29, 2026

addedInput schema / properties / inventory_id / description

Added value: +"The item id from add_inventory_item, get_inventory or search_inventory."

addedOutput schema / properties / capability_summary

Added value: +{
+  "description": "One line to plan from: the item, its stored specs, and its last observed state with its date.",
+  "type": "string"
+}

changedOutput schema / properties / item / description

Previous value: -"Inventory item record."New value: +"Inventory item record. With specs: spec_template, specs, state (a timestamped snapshot), state_freshness and capability_summary."

addedOutput schema / properties / people

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds information not present in structured fields: a $0.10 cost, an API-key requirement, and how to interpret state_freshness including a caution about stale values. It does not describe caching, rate limits, or pagination, so it stops short of full transparency.

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?

A single front-loaded sentence that names the resource first and then enumerates contents, with cost/auth tacked on at the end so they are not buried. Dense but mostly waste-free; the parenthetical example question is slightly indulgent.

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?

An output schema exists, so return values need no prose explanation, and the description still covers cost, auth, and the freshness caveat an agent needs before acting. Nothing required to call this correctly is missing.

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

Parameters3/5

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

Only one parameter and schema coverage is 100%, so the schema already documents inventory_id and its origin tools. The description adds no parameter-level detail beyond that, which matches the baseline 3 when structured fields do the heavy lifting.

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?

States a specific verb and resource with explicit scope: 'One owned Inventory item in full', and enumerates the exact payload (specs, spec_template, state/state_freshness, capability_summary, valuations, people, photos). This clearly separates it from get_inventory (list), search_inventory (search), and update_inventory_item (mutation).

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?

Usage is implied (single-item detail fetch by id supplied from add_inventory_item, get_inventory, or search_inventory in the schema). It offers one genuine conditional instruction — check with the user before relying on stale state — but never names an alternative tool or states when to prefer this over get_inventory or search_inventory.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.