Skip to main content
Glama
Sign In
context-keeper

context-keeper

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

export_snapshot

Create a compressed, git-committable snapshot of project memory for team sharing, leaving the working store unchanged.

Instructions

Write the whole store to a compressed, committable snapshot at .context-keeper/memory.json.gz (next to the project) and add a .gitattributes merge=ours guard. For sharing project memory with a team via git. Committing it is opt-in. Non-destructive to the working store.

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

Input Schema

NameRequiredDescriptionDefault
project_dirNoAbsolute path to the target project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that the operation is non-destructive and specifies the exact file location and .gitattributes modification. With no annotations, the description adequately covers key behavioral traits.

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?

Two concise sentences with no fluff. The action is stated first, then purpose and side effects. Every sentence is meaningful.

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 tool with one parameter and no output schema, the description covers the action, output location, side effects, and use case. It does not mention return value or error scenarios, but these are less critical for an export tool.

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?

The schema already describes the single parameter, but the description adds value by explaining that the snapshot is placed next to the project, which provides context about how the parameter is used.

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 exports the whole store to a compressed snapshot at a specific path, and adds a .gitattributes guard. It distinguishes from sibling tools like import_snapshot and mirror.

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?

Explicitly states 'For sharing project memory with a team via git', providing a clear use case. However, it does not explicitly contrast with alternatives like import_snapshot or describe when not to use it.

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