Skip to main content
Glama

log_session_summary

Log a session handoff summary when finishing work in one AI agent so the next agent can continue from clear next steps, active files, and workspace context.

Instructions

Log a session handoff summary when finishing work in one AI agent (e.g. Antigravity) so the next agent (e.g. OpenCode or Codex) can continue seamlessly.

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": {
      "summary": "<summary>"
    },
    "name": "log_session_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYesSummary of what was accomplished in this session.
workspaceNoProject workspace identifier.
next_stepsNoActionable next steps for the next coding session or AI agent.
active_filesNoList of file paths that were created or modified during this session.
source_agentNoAI agent logging the session (e.g. 'antigravity', 'opencode', 'codex').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations at all, so the description carries the full burden. It does disclose the key behavioral trait that the entry is meant to be picked up by a different agent later, implying durable cross-session storage, but it says nothing about permissions, repeat-call/overwrite behavior, or what is returned.

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?

One sentence, front-loaded with the action and resource, with the motivating purpose trailing it. Nothing is redundant or padded.

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

Completeness3/5

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

For a simple logging tool with a fully documented schema, the purpose and trigger are covered. However, with no annotations and no output schema, the agent still cannot tell what the call returns or whether repeated logging overwrites or appends, which leaves a real 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 all five parameters are already documented in structured data. The description only adds the concrete agent-name examples (Antigravity, OpenCode, Codex) that clarify source_agent; otherwise it is baseline.

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?

Specific verb+resource ('Log a session handoff summary') plus the intent ('so the next agent can continue seamlessly'), so the agent knows exactly what is produced. It does not contrast itself with siblings like remember_decision or compact_memories, which is the only thing keeping it off 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?

Gives a clear trigger condition: 'when finishing work in one AI agent'. That is enough to know when to call it, but there are no exclusions and no named alternative for mid-session persistence or decision recording.

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