Skip to main content
Glama
gitmem-dev

GitMem

Official
by gitmem-dev

session_close

Persist session reflections and compliance data to close a session. Supports file-based or inline payload, auto-generating task completion.

Instructions

Persist session with compliance validation. Two modes: (1) Write closing_reflection and other payload to {gitmem_dir}/closing-payload.json, then call with session_id + close_type. (2) Pass closing_reflection directly as a parameter (simpler). Both work — inline params override file payload. task_completion is auto-generated. DISPLAY: Output the display field verbatim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
close_typeYesType of close (standard requires full reflection)
session_idYesSession ID from session_start
linear_issueNoAssociated Linear issue
human_correctionsNoHuman corrections or 'none'
closing_reflectionNoSession reflection (alternative to writing closing-payload.json). Keys: what_broke, what_took_longer, do_differently, what_worked, wrong_assumption, scars_applied, institutional_memory_items, collaborative_dynamic, rapport_notes
ceremony_duration_msNoEnd-to-end ceremony duration from agent perspective (in milliseconds)
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool persists with compliance validation, auto-generates task_completion, and instructs to output the display field verbatim. It does not detail side effects or authentication needs, but the key behavioral aspects are covered.

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?

The description is concise (four sentences) and front-loaded with purpose. Every sentence provides essential information without redundancy or fluff.

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?

Given the tool's complexity (6 parameters, no output schema), the description is reasonably complete: it explains modes, inline override, auto-generation of task_completion, and display instructions. It could be improved by specifying the output format, but it covers the most critical context for an agent.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the two operational modes and the relationship between file payload and inline parameters, which goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool persists a session with compliance validation, and it distinguishes from sibling session tools (session_start, session_refresh) by focusing on closure. The two modes are explicitly described, making the purpose specific and unambiguous.

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?

The description provides explicit usage guidance for two modes (file-based vs inline), including the fallback rule (inline overrides file). However, it does not specify when NOT to use this tool or mention alternative tools for similar tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitmem-dev/gitmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server