Skip to main content
Glama

Get Last Handoff

get_last_handoff

Retrieve the current AI handoff document so a new AI session gains full project context and can resume work.

Instructions

Retrieve the most recent AI handoff document so a new AI session has full context.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'retrieve' implies a read-only operation, but the description does not explicitly state that it has no side effects, what happens if no handoff document exists, or whether any permissions are required. The presence of an output schema reduces the need to describe return values, but behavioral disclosure remains thin.

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?

The description is a single front-loaded sentence that states the action, the resource, and the reason for using it. There is no redundant wording or unnecessary detail.

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?

Given the tool's low complexity (one optional parameter) and the existence of an output schema, the description is largely complete for invoking the tool correctly. It could say more about edge cases, such as when no handoff exists, and about how it relates to sibling tools like list_handoffs, but the core purpose and motivation are covered.

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 parameter is documented in the schema as 'Project root directory' with a default of '.'. The description adds no meaning about how the path parameter affects retrieval or what root directory means in this context, so the baseline of 3 is appropriate.

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 uses a specific verb ('Retrieve') and a specific resource ('most recent AI handoff document'), and it states the purpose of giving a new AI session full context. It implicitly distinguishes itself from list_handoffs and generate_handoff through the 'most recent' scope, though it does not name those siblings explicitly.

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?

The phrase 'so a new AI session has full context' implies the tool should be used at the start of a session, but the description does not state explicit when-to-use or when-not-to-use conditions. It also does not name alternatives such as list_handoffs or start_session that an agent might choose instead.

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