Skip to main content
Glama
Sign In
claude-engram

claude-engram

by 20alexl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_end

Review a recap of session activities, including tracked mistakes, decisions, and context. Memories save automatically; use for a concise summary.

Instructions

Optional. Shows session summary. All memories auto-save without this - just a nice recap.

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

Input Schema

NameRequiredDescriptionDefault
project_pathNoProject directory (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description bears full responsibility. It transparently states the tool is optional, shows a summary, and doesn't affect memory saving. No negative traits like destruction or auth needs are mentioned, which is appropriate for a harmless tool.

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 extremely concise with one sentence that front-loads the key purpose ('Optional. Shows session summary.') and adds clarifying context. No wasted words.

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 optional tool, the description covers the essential purpose and clarifies it's a recap. No output schema exists, but the description implies the output is a summary, which is sufficient. Lacks mention of the parameter, but given its optionality and schema coverage, it's adequate.

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?

There is one optional parameter 'project_path' with 100% schema description coverage. The tool description does not add any extra meaning beyond what the schema already provides, so baseline score of 3 applies.

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 it 'shows session summary', specifying the verb and resource. It distinguishes itself from sibling tools like 'session_start' and 'session_mine' by indicating it's a recap, not a start or mine.

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 marks it as 'Optional' and clarifies that memories auto-save without it, implying it's for a recap only. While it doesn't explicitly state when to use or alternatives, the context is clear that it's not required.

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