Skip to main content
Glama

End Session

end_session

Finalize the active session by saving a summary, progress updates, and known issues, then generate a handoff file without auto-committing changes.

Instructions

End the current session, update progress, and generate a handoff file (does not auto-commit changes).

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_summary": "<session_summary>"
    },
    "name": "end_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
known_issuesNo
session_summaryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/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 disclose two important behaviors: it mutates session progress state and writes a handoff file, but does not commit. That is real added value. It omits whether the session is terminated afterward, where the handoff file is written, and whether prior session state is discarded.

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?

A single front-loaded sentence with the primary action first, secondary effects second, and the key constraint in a parenthetical. No filler or redundancy.

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?

An output schema exists, so return-value explanation is not required. But for a state-mutating lifecycle tool with zero annotation coverage and 0% parameter documentation, the description is thin — it should at minimum explain what session_summary is for and what happens to the session after ending.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all 3 parameters, and the description compensates for none of them. The required 'session_summary' parameter — the single mandatory input — is never mentioned, nor is 'known_issues' or 'path', so the agent gets no guidance on what content these expect.

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 and resource ('End the current session') and names the concrete effects: progress update and handoff file generation. It implicitly distinguishes itself from start_session and commit_changes via the parenthetical, though it never names 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 parenthetical '(does not auto-commit changes)' implies the agent must separately invoke a commit tool, which is useful implied usage. However there is no explicit when-to-use guidance, no prerequisite conditions (e.g., must a session be active?), and no routing to generate_handoff or prepare_commit as alternatives.

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