Dayze — Life Context

Get Time Capsules

get_time_capsules

Read-only

The user's time capsules by open date. status pending, delivered or all (default). A capsule still sealed shows its date and no message, as in the app, even to the owner. Reading opens nothing. ($0.05; API key required)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_time_capsules"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Capsule state filter: all, pending or delivered, e.g. pending.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026
- addedInput schema / properties / status / description
```
Added value: +"Capsule state filter: all, pending or delivered, e.g. pending."
```
AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/destructive annotations, the description discloses two genuinely useful behaviors: sealed capsules expose only a date and no message even to the owner, and reading does not open a capsule. It also states cost ($0.05) and auth requirements (API key), which annotations cannot convey.

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?

Compact and front-loaded: purpose first, then filter values, then the sealed-capsule caveat, then cost/auth. The telegraphic fragments ('The user's time capsules by open date') cost a little readability but nothing is wasted.

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?

For a single-parameter read tool with an output schema, the description covers purpose, filter semantics, the surprising sealed-capsule behavior, and cost/auth. Only pagination or result-size behavior is absent, which is minor here.

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 100% and the single enum parameter is already documented, so the baseline is 3. The description's main addition is declaring 'all' as the default, which the schema does not state.

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+resource ('The user's time capsules') and adds scoping ('by open date'), which lets an agent distinguish this read from create_time_capsule. It stops short of explicitly contrasting with any sibling, so it is clear but not maximally differentiated.

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 status enumeration ('pending, delivered or all (default)') implies the filtering use case, and 'Reading opens nothing' hints that inspecting capsules is safe/idempotent. However, there is no explicit when-to-use statement or routing to alternatives such as create_time_capsule.

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.