perseus

perseus_context_diff

Read-onlyDestructive

Show changes since last session including git updates, task-board changes, messages, checkpoints, and memories. Use at document top to avoid re-orienting on unchanged state.

Instructions

Render a compact 'Since last session' delta (#714): git branch/commits, Agora task-board changes, new inbox messages, new checkpoints, and new vault session memories since the last recorded snapshot. Use at the top of a context document so the assistant spends zero turns re-orienting on unchanged state. Maintains its own per-workspace snapshot (refresh debounced by render.context_diff_min_age_s); reset=true forces a new baseline. Never cached.

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": "perseus_context_diff"
  }
}

Input Schema

Name	Required	Description	Default
`reset`	No	Value for reset parameter

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.22Jul 11, 2026

TDQS

A3.8/5.0

Behavior1/5

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

Description claims read-only operation ('Render a compact delta', 'Never cached'), but annotations declare destructiveHint=true, creating a direct contradiction. Additionally, description mentions snapshot maintenance and debounce, but the contradiction overrides.

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 sentences, no wasted words. Front-loaded with main purpose, followed by usage context and behavioral details. Highly efficient.

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?

Describes output content in detail (git, task-board, inbox, etc.), mentions snapshot and debounce behavior. No output schema, but description compensates reasonably. Could mention default state or what happens with no changes.

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

Parameters4/5

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

Schema description for 'reset' is vague ('Value for reset parameter'). Description adds meaning: 'reset=true forces a new baseline,' clarifying its effect. Schema coverage is 100% but description enhances understanding.

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?

Description clearly states it renders a compact 'Since last session' delta and lists specific items included (git branch/commits, Agora task-board changes, new inbox messages, etc.). It distinguishes itself from sibling tools by focusing on session changes.

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?

Explicitly advises to use at the top of a context document to avoid re-orientation. Mentions reset parameter for baseline reset. Lacks explicit when-not or alternative tool comparisons, but context is clear.

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