Dayze — Life Context

Preview Memory Duplicates

preview_memory_duplicates

Read-only

Group exact agent-memory duplicates first, then near duplicates (same normalized content as context-pack collapse) for human review. Never merges. Use merge_memory for exact groups and merge_near_memory for near groups. ($0.10; 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": "preview_memory_duplicates"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max active memories to scan (1–500, default 200).

Output Schema

Name	Required	Description	Default
`scanned`	No
`auto_merged`	Yes
`near_groups`	Yes
`exact_groups`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is largely covered, but the description adds non-obvious context: the operation 'Never merges,' carries a $0.10 cost, and requires an API key. It does not describe ordering/grouping output shape, though an output schema exists to cover that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core behavior, then the non-mutation guarantee, then the routing guidance. The parenthetical cost/auth note is compact and every clause contributes distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one optional parameter, full schema coverage, an output schema, and safety annotations, the description supplies exactly the missing pieces: it is a read-only preview, it never merges, which sibling to use next, and the cost/auth prerequisites. Nothing an agent needs in order to call this correctly is absent.

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 description coverage is 100% and the single 'limit' parameter already documents its range and default of 200, so the description is not obligated to restate it. It adds only the implicit notion that scanning is bounded ('Max active memories to scan'), with no extra semantics about how limiting interacts with grouping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Group exact agent-memory duplicates ... then near duplicates') and immediately disambiguates itself from the merge siblings by stating 'Never merges.' An agent can distinguish this preview tool from merge_memory and merge_near_memory without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: 'Use merge_memory for exact groups and merge_near_memory for near groups,' which states both alternatives and the condition that selects each. The 'for human review' clause further frames this as the inspection step preceding a merge decision.

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.