Skip to main content
Glama

List Handoffs

list_handoffs

Lists all AI session handoffs and their dates for a project root, helping you review past session transitions and resume work.

Instructions

List all AI session handoffs with dates.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read-only listing. It does not say where handoffs are read from, how they are ordered, whether truncation or limits apply, or whether a projects without handoffs errors or returns empty.

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

Conciseness4/5

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

One short, front-loaded sentence with no filler or redundancy. Its brevity is close to under-specification, but as a sentence it is efficient and easy to parse.

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?

Not applicable as written; the tool is a low-complexity single-parameter listing operation, and an output schema exists so return values need no explanation. Still missing is the ordering/scope detail that would let an agent know exactly what it gets back relative to get_last_handoff.

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?

The single optional path parameter is fully documented in the schema (100% coverage) as "Project root directory," so the schema does the heavy lifting. The description adds no further meaning about how path affects which handoffs are listed, which is the baseline expectation here.

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?

"List all AI session handoffs" gives a specific verb plus resource, and it is identifiable against siblings like generate_handoff and get_last_handoff. It stops short of stating the distinguishing scope (e.g., all handoffs vs. only the most recent one), so the differentiation is only implicit.

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?

There is no when-to-use guidance at all: nothing says to call this instead of get_last_handoff when you want history, and no prerequisites or exclusions are given. The agent must infer the use case from the name alone.

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