Novyx MCP

Official

by novyxlabs

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

replay_diff

Read-only

Detect differences in memory state between two timestamps, highlighting added, removed, and modified items.

Instructions

Diff memory state between two timestamps.

Shows what was added, removed, and modified in a time range.
Requires Pro tier or Novyx Cloud.

Args:
    start: Start timestamp (ISO).
    end: End timestamp (ISO).

Returns:
    JSON string with added, removed, and modified memories.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "replay_diff"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.4Mar 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations indicate readOnlyHint=true, consistent with a read operation. The description details the output (JSON with added/removed/modified), adding meaningful behavioral context beyond annotations.

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?

Four sentences, front-loaded with purpose, then requirements, then arguments. No wasted words.

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?

Given two simple parameters and an output schema, the description covers purpose, usage constraint, input format, and output format. Fully adequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It explicitly states each parameter's format (ISO timestamp), which adds crucial meaning beyond the schema's type string.

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 clearly states it diffs memory state between two timestamps and shows added/removed/modified. This is specific and distinguishes from siblings like replay_snapshot and replay_timeline.

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

Usage Guidelines4/5

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

It mentions the requirement of Pro tier or Novyx Cloud, providing a usage constraint. It does not explicitly contrast with sibling tools, but the purpose is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.