memory-manager-mcp

Get latest handoff

get_latest_handoff

Retrieve the most recent handoff for a project, with an option to include historical handoff records.

Instructions

Retrieve the most recent handoff for the project.

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_latest_handoff"
  }
}

Input Schema

Name	Required	Description	Default
`history`	No	Also include recent handoff history.
`workspacePath`	No	Workspace directory of the project. Defaults to the server working directory.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 17, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, but it only states that the tool retrieves the most recent handoff. It does not disclose whether this is read-only, how the history flag affects behavior, or what happens if no handoff exists. This is minimal transparency.

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

Conciseness3/5

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

The description is a single short sentence and is not verbose, but it essentially restates the title ('Get latest handoff' vs 'Retrieve the most recent handoff'), adding no new information and thus not fully earning its place.

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

Completeness2/5

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

For a simple tool with no output schema and no annotations, the description is underdeveloped. It does not explain the significance of the history flag, the default workspace path behavior, or how this differs from similar retrieval tools, leaving the agent with insufficient context to invoke it correctly.

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 both parameters (history, workspacePath) are already described in the schema. The description adds no additional meaning about the 'project' context or how the parameters affect the result, so it meets the baseline without compensating further.

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 uses a specific action ('Retrieve') and resource ('the most recent handoff'), clearly distinguishing it from sibling tools like create_handoff and get_project_context. It precisely states the tool's function without ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as create_handoff or get_project_context. It lacks any context about scenarios, prerequisites, or exclusions.

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

Deploy Server