Dayze — Life Context

Get Shared Memories

get_shared_memories

Read-only

Memories the user shares with connections: each invitation's direction (shared or received), the other person, status and dates. For ones the user shared, the moments in it. Moments someone else shared are not returned: they stay in the app. Read only: this cannot invite, accept or revoke. ($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_shared_memories"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Invitation state filter: pending, accepted or revoked, e.g. pending.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026
- addedInput schema / properties / status / description
```
Added value: +"Invitation state filter: pending, accepted or revoked, 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?

Goes beyond the annotations by disclosing practical constraints: read-only semantics spelled out as 'cannot invite, accept or revoke', a $0.05 cost, an API key requirement, and a data-visibility rule about other people's moments. The annotations already cover safety, so this extra cost/auth/exclusion context is real added value.

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 – the returned fields are stated before the exclusions and the pricing/auth note. The telegraphic list style ('each invitation's direction... the other person, status and dates') is efficient, though slightly clipped.

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 shapes need not be described, and the description still covers scope, exclusions, read-only behavior, cost and auth. Only minor gap is the absence of any note on the status filter's default behavior.

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 status parameter already documents its enum values with an example, so the schema carries parameter meaning. The description never mentions the status filter or what the default (no filter) returns, so it adds nothing beyond the schema.

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?

The description names a specific resource and scope: memories the user shares with connections, including invitation direction, the other person, status and dates. It implicitly separates itself from get_memories by narrowing to shared/invitation records, though it never names the sibling or explicitly contrasts the two.

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 ('memories the user shares with connections') and it carves out what is excluded ('moments someone else shared are not returned: they stay in the app'). There is no explicit when-to-use statement or named alternative for retrieving the user's own unshared memories.

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.