Skip to main content
Glama
Sign In
context-keeper

context-keeper

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_compaction_report

Detect and surface discrepancies if the last compaction lost or modified context entries. Verify integrity before proceeding.

Instructions

Check if the last compaction lost or modified any context entries. Surface discrepancies to the user before proceeding.

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

Input Schema

NameRequiredDescriptionDefault
project_dirNoAbsolute path to another project to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It implies a read-only check ('Check if...') but does not explicitly declare safety or side effects, leaving some ambiguity about whether it modifies state.

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 sentences directly convey the core purpose, with no filler words. The description is front-loaded and efficient.

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

Completeness3/5

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

The description lacks details about the return format (e.g., list of discrepancies or boolean) and does not explain the 'report' concept. Given no output schema, this omission reduces completeness.

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%, and the parameter description ('Absolute path to another project to check') is self-explanatory. The tool description adds no further meaning, meeting the baseline for simple parameters.

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 checks for loss or modification from the last compaction and surfaces discrepancies, which is a specific verb+resource. It implicitly distinguishes from sibling tools like verify_quality or prune_stale by focusing on compaction aftermath.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before proceeding' gives a hint of when to use, but there is no explicit guidance on when not to use or alternatives among siblings, leaving the agent to infer usage context.

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