Skip to main content
Glama
Sign In
@contextq/mcp

@contextq/mcp

Official
by contextq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_handoff

Generate a workspace handoff document at session end to capture progress, next steps, and open questions. Links context to the session and can mark it completed.

Instructions

Generate a handoff document for the session's workspace at run end (wraps the dream handoff generator — LLM-synthesized TL;DR + in-progress + next-steps + open-questions). Links the handoff context back to the session. Pass complete=true to also mark the session completed. Requires an LLM provider configured on the server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "agent_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoGenerate without persisting the handoff context
projectNoOptional project slug to narrow the handoff
completeNoAlso set the session status to 'completed'
workspaceNoWorkspace slug (falls back to the session's workspace)
session_idYesSession to generate a handoff for
since_daysNoLook-back window in days (default 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the LLM-synthesized nature, that handoff context is linked back to the session, the side effect of complete=true marking the session completed, and the hard prerequisite of a configured LLM provider. It omits reversibility of the completed status and any auth/permission needs.

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?

Three sentences, front-loaded with what is produced and finished with the prerequisite; the parenthetical content list is information-dense rather than filler. Slightly packed but every clause earns its place.

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 6-param, no-annotation, no-output-schema mutation tool, the description covers the artifact produced, the main side effect, and the LLM prerequisite. It does not describe what happens to the returned handoff or how errors surface when no provider is configured, leaving a small gap.

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%, so every parameter (dry_run, project, complete, workspace, since_days, session_id) is already documented in the schema. The description only reiterates complete=true and adds that workspace falls back to the session's workspace implicitly; baseline 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?

States a specific verb+resource ('Generate a handoff document for the session's workspace') and enumerates contents (TL;DR, in-progress, next-steps, open-questions), so an agent knows exactly what artifact is produced. It does not explicitly differentiate itself from nearby siblings like agent_checkpoint or agent_session_end, which is the only thing keeping it from a 5.

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?

Clear context: call 'at run end', and pass complete=true to additionally close the session. It also states the prerequisite that an LLM provider must be configured. No explicit when-not or named alternative to sibling tools, so it stops short of a 5.

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

Deploy Server

Other Tools