Dayze — Life Context

Search Inventory

search_inventory

Read-only

Search owned Inventory by name, brand, model, notes or reference number (query), with the same filters as get_inventory. Returns photo_count, has_photos, cover_url; when empty, photo_hint explains upload_asset linkage. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	1-200, default 50
`query`	No	Match name, brand, model, notes or reference number.
`offset`	No
`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
`query`	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"
+]

Changed10 schema fields changedSep 29, 2026

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

addedInput schema / properties / category

Added value: +{
+  "description": "e.g. electronics, watches, 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": "API keys only: include stored identifiers. Ignored for connectors without pii:read.",
+  "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 / query / description

Added value: +"Match name, brand, model, notes or reference number."

addedInput schema / properties / sort_by

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

addedInput schema / properties / status

Added value: +{
+  "description": "wishlist | ordered | owned | listed_for_sale | sold | returned | lost | disposed | donated | archived",
+  "type": "string"
+}

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."

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 the safe read-only, non-destructive, closed-world profile. The description adds value on top: a cost ($0.10), an auth requirement (API key), and the special empty-result behavior where photo_hint explains the upload_asset linkage. It does not cover pagination or rate behavior, but the additions are meaningful given annotations carry safety.

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?

One front-loaded sentence packs scope, match fields, output fields, edge-case behavior, cost, and auth without redundancy. The parenthetical cramming is dense but every clause earns its place; no filler sentences.

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?

An output schema exists, so return values needn't be explained, yet the description still flags photo_count/has_photos/cover_url and the empty-case photo_hint. Cost and auth are disclosed. The one gap is that 'same filters as get_inventory' offloads filter semantics to a sibling the agent must look up, which weakens completeness for this 8-param tool.

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%. The description reinforces the query field's match set (name, brand, model, notes, reference number), which aligns with the schema. It adds no syntax or defaults for limit/offset/sort_by/status/category/include_archived/include_sensitive, so it only marginally compensates for the coverage gap; baseline 3.

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 (Search) and resource (owned Inventory) and enumerates the searchable fields via the query parameter. It gestures at differentiation from get_inventory ('same filters as get_inventory') but never plainly states what search does that get_inventory doesn't, leaving that inference to the agent.

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: use this to match against name/brand/model/notes/reference. The reference to get_inventory's filters hints at a sibling relationship but gives no explicit when-to-use-this-vs-get_inventory/when-not rule or exclusions, so routing is left partly to inference.

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.