Skip to main content
Glama

What the next session gets

next_session_handoff
Read-onlyIdempotent

Returns the handoff data a new coding session gets from a repository, including carried memories, whether handoff is enabled, and the quote passage timestamp.

Instructions

What Caprock hands a new session started in a repository: the Second Brain memories it carries, whether the handoff is switched on, and when the passage it would quote was written.

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

Input Schema

NameRequiredDescriptionDefault
repoNoA directory inside the repository; defaults to the directory this server was started in (normally the project the agent is working in).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful content-level disclosure (memories carried, whether handoff is switched on, passage timestamp), but it does not describe the response shape or what happens when the handoff is off or the repo is invalid.

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?

It is a single front-loaded sentence with no redundant wording, and the three returned facts are enumerated compactly. The phrasing is slightly ornate ('the passage it would quote') but not wasteful.

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?

For a simple, one-optional-parameter read tool with rich annotations and no output schema, the description names the three pieces of information returned, which is enough to decide whether to call it. It stops short of explaining result structure or edge-case behavior, but nothing critical is missing.

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?

With a single optional parameter and 100% schema description coverage, the schema already explains the repo default. The description adds nothing about the repo argument, so the baseline 3 applies.

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 names a specific resource and scope: what Caprock hands a new session in a repository, enumerating the memories, the enabled flag, and the passage timestamp. That is clearly a read/inspect operation rather than a mutation, though it never explicitly contrasts itself with siblings like session_summary or recent_sessions.

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 and no mention of alternatives. An agent can infer that this previews the next session's handoff, but the description never states the conditions that select it over session_prose, session_summary, or recent_sessions.

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