Skip to main content
Glama
Sign In

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Create Time Capsule

create_time_capsule

Seal a message to the future self until deliver_on_date, a date after today in the account timezone. The message cannot be read back until then. ($0.10; API key required)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>",
      "deliver_on_date": "<deliver_on_date>"
    },
    "name": "create_time_capsule"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage to the future self, e.g. Remember how good this year felt.
request_idNoClient idempotency key (retries return original result).
deliver_on_dateYesYYYY-MM-DD, after today.
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
capsuleNo
messageNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / message / description
      Added value: +"Message to the future self, e.g. Remember how good this year felt."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare this is a non-destructive, non-open-world write; the description adds meaningful behavior beyond them: the sealed content is unreadable until the delivery date, each call costs $0.10, and an API key is required. It doesn't say what happens on an invalid/past date or whether a capsule can be cancelled.

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?

Three tight sentences, front-loaded with the core action and constraint, with cost/auth tacked on parenthetically. No wasted wording.

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?

Output schema exists so return values needn't be explained, and cost, auth, and the sealing constraint are covered. Only edge-case behavior (invalid date, cancellation) is missing, a minor gap for a 4-parameter create 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 100%, so the baseline is 3. The description adds the account-timezone qualifier for deliver_on_date, but says nothing about request_id/idempotency_key semantics that the schema already covers.

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?

Specific verb-plus-resource ("Seal a message to the future self") with a clear temporal condition. It contrasts implicitly with the sibling get_time_capsules by stressing the message "cannot be read back until then," though it never names the reader counterpart.

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?

Gives an implicit when-to-use (creating a sealed future message) and a hard constraint that deliver_on_date must be after today in the account timezone. It offers no explicit when-not guidance or pointer to get_time_capsules for retrieval.

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

Resources