Dayze — Life Context

Get Inventory

get_inventory

Read-only

Browse the user's owned Inventory: filter by category, status or search text (name, brand, model, notes, reference number). Archived and no-longer-owned items only with include_archived. Items with specs carry capability_summary and state_freshness; each item has photo_count and cover_url. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-200, default 50
`offset`	No
`search`	No	Match name, brand, model, notes or reference number.
`status`	No
`sort_by`	No
`category`	No	e.g. electronics, watches, clothing
`include_archived`	No	Include archived and no-longer-owned items.
`include_sensitive`	No	API keys only: include stored identifiers. Ignored for connectors without pii:read.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

removedInput schema / properties / status / description

Removed value: -"wishlist | ordered | owned | listed_for_sale | sold | returned | lost | disposed | donated | archived"

addedInput schema / properties / status / enum

Added value: +[
+  "wishlist",
+  "ordered",
+  "owned",
+  "listed_for_sale",
+  "sold",
+  "returned",
+  "lost",
+  "disposed",
+  "donated",
+  "archived"
+]

Changed7 schema fields changedSep 29, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / category / description

Previous value: -"e.g. watches, electronics, clothing"New value: +"e.g. electronics, watches, clothing"

changedInput schema / properties / include_archived / description

Previous value: -"Include archived and no-longer-owned items"New value: +"Include archived and no-longer-owned items."

changedInput schema / properties / include_sensitive / description

Previous value: -"Include serial numbers"New value: +"API keys only: include stored identifiers. Ignored for connectors without pii:read."

changedInput schema / properties / search / description

Previous value: -"Match name, brand, model, notes or reference number"New value: +"Match name, brand, model, notes or reference number."

changedInput schema / properties / status / description

Previous value: -"e.g. owned, wishlist, sold"New value: +"wishlist | ordered | owned | listed_for_sale | sold | returned | lost | disposed | donated | archived"

changedOutput schema / properties / items / items / 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."

Changed8 schema fields changedSep 29, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "e.g. watches, electronics, clothing",
+  "type": "string"
+}

addedInput schema / properties / include_archived

Added value: +{
+  "description": "Include archived and no-longer-owned items",
+  "type": "boolean"
+}

addedInput schema / properties / include_sensitive

Added value: +{
+  "description": "Include serial numbers",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "1-200, default 50",
+  "type": "number"
+}

addedInput schema / properties / offset
```
Added value: +{
+  "type": "number"
+}
```

addedInput schema / properties / search

Added value: +{
+  "description": "Match name, brand, model, notes or reference number",
+  "type": "string"
+}

addedInput schema / properties / sort_by

Added value: +{
+  "enum": [
+    "created_at",
+    "name",
+    "value"
+  ],
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "e.g. owned, wishlist, sold",
+  "type": "string"
+}

AddedSep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this a non-destructive read in a closed world, so the bar is lower; the description still adds useful operational context: archived/no-longer-owned items are excluded by default, spec-bearing items return capability_summary and state_freshness, and the call costs $0.10 with an API key. It does not cover pagination behavior.

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 dense paragraph that front-loads the browse+filter purpose, then scope caveats, then return-field hints and cost/auth. Every clause carries information, though the return-field detail is partly redundant with the output schema.

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?

With an output schema present, return values need not be re-explained, and the description still adds cost, auth, default-exclusion behavior, and filter semantics. Only pagination (limit/offset interaction) and include_sensitive handling are left implicit.

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?

Schema coverage is 63%, and the description adds real meaning for search (which fields are matched) and restates include_archived's effect. However limit/offset/sort_by, the status enum values, and especially include_sensitive are left entirely to the schema, so the description only partially compensates for the coverage gap.

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?

States a specific verb (browse) and resource (the user's owned Inventory) plus the three filter axes, so the agent knows this is a filtered list operation. It is distinguishable from get_inventory_item by its plural/browse framing, though it never names the very similar search_inventory sibling.

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 filter conditions imply usage, but there is no explicit when-to-use/when-not guidance relative to search_inventory or get_inventory_item, which are the obvious alternatives in a sibling list of this size. The include_archived note hints at scope but is a parameter rule, not selection guidance.

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.