Skip to main content
Glama
Sign In
context-keeper

context-keeper

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

import_snapshot

Import committed project memory snapshot into the working store. Non-destructive: leaves existing entries untouched, runs automatically when store is empty.

Instructions

Import the committed .context-keeper/memory.json.gz snapshot into the working store. Non-destructive: a store that already has entries is left untouched. Runs automatically on first use when the store is empty.

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": "import_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.2/5.0
Behavior4/5

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

Describes key behavioral traits (non-destructive, auto-run) given no annotations. Could expand on prerequisites or failure modes but sufficient.

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?

Three concise sentences, fully front-loaded with purpose and key behavior. No extraneous text.

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?

Covers essential behavior for a simple tool with one parameter. Missing return value info but acceptable given no output schema.

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 already fully describes parameter ('project_dir') with 100% coverage; description adds no additional semantics.

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?

Clearly states the action (import) and resource (snapshot file). Distinguishes from siblings like export_snapshot.

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?

Specifies non-destructive behavior and auto-run condition, but lacks explicit guidance on manual use cases or when to prefer this over alternatives.

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