claude-engram

Overview Schema Source Related Servers Discussions Admin

session_start

Load full context including memories, checkpoints, decisions, and memory health for a project. Auto-cleans duplicates and provides deep session context beyond basic hook auto-start.

Instructions

Load full context: memories, checkpoints, decisions, memory health. Auto-cleans duplicates. Hook auto-starts basic session, but this gives deep context.

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": {
      "project_path": "<project_path>"
    },
    "name": "session_start"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	Project directory path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'auto-cleans duplicates' which implies mutation, but does not clarify whether the tool is read-only or modifies state. No disclosure of auth needs, rate limits, or side effects beyond cleanup.

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?

The description is two sentences, front-loaded with the core purpose, and uses clear language. It is efficient but could be more structured for skimming.

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

Completeness2/5

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

The tool has no output schema, so the description should explain return values or side effects. It mentions auto-cleaning duplicates but does not describe what the tool returns or any prerequisites. Incomplete for a tool that loads context.

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% for the single parameter 'project_path'. The description does not add any meaning beyond the schema's 'Project directory path' explanation. Baseline score of 3 applies as no extra value is provided.

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 loads full context including memories, checkpoints, decisions, and memory health. It differentiates from a basic session start by noting the hook auto-starts basic session but this gives deep context.

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 implies when to use this tool (when deep context is needed) versus the hook (basic session). It does not explicitly list when not to use or mention alternatives like session_mine, but provides sufficient guidance.

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