Skip to main content
Glama
timgordontg

engrim

by timgordontg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engrim_review

Check conversation and flight recorder history before clearing context to surface unsaved architectural decisions. Returns a safe-to-clear verdict and uncaptured candidate records.

Instructions

Read-only check: Inspect conversation and flight recorder history before clearing context to surface recent architectural decisions not yet saved to curated memory. Safe to call with no side effects. Returns heuristic verdict (safe_to_clear: true/false/null) and uncaptured candidate records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoProject identifier tag; 'auto' infers from current working directory repository root.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes
projectYes
uncapturedYes
safe_to_clearYes
scanned_turnsYes
active_curatedYes
total_log_turnsYes
uncaptured_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Coverage verdict plus uncaptured decision candidates (safe_to_clear is null when no transcript log exists).",
+  "properties": {
+    "active_curated": {
+      "type": "integer"
+    },
+    "message": {
+      "type": "string"
+    },
+    "project": {
+      "type": "string"
+    },
+    "safe_to_clear": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "scanned_turns": {
+      "type": "integer"
+    },
+    "total_log_turns": {
+      "type": "integer"
+    },
+    "uncaptured": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "uncaptured_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "project",
+    "total_log_turns",
+    "scanned_turns",
+    "active_curated",
+    "safe_to_clear",
+    "uncaptured_count",
+    "uncaptured",
+    "message"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changedv1.4.2
    • changedInput schema / properties / project / description
      Previous value: -"Project tag; 'auto' = current working directory."New value: +"Project identifier tag; 'auto' infers from current working directory repository root."
    • addedInput schema / required
      Added value: +[]
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description takes full responsibility for behavior. It explicitly discloses read-only status, 'no side effects', and a heuristic verdict that may be null, plus the uncaptured-candidate output. This gives an agent an accurate safety and expectation model.

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 two tightly packed sentences, with the safety qualifier and primary action front-loaded before the return-value detail. Every clause earns its place.

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 single-optional-parameter tool with an output schema, the description covers purpose, safety, and return-value shape. It could be slightly stronger by explicitly routing away from sibling tools like engrim_recall or engrim_add, but the core call is complete.

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 only optional parameter, project, already has a clear description including the 'auto' inference behavior. The tool description adds no additional parameter information, but none is needed because the schema carries it.

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?

Description opens with a specific verb and resource ('Inspect conversation and flight recorder history') and states the exact purpose: surface architectural decisions not yet saved before clearing context. It differentiates from sibling tools by its read-only review/heuristic-verdict role rather than recall/context/add.

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 phrase 'before clearing context' gives a concrete trigger for when to invoke the tool. It does not explicitly name comparison alternatives or when-not-to-use conditions, but the intended workflow position is clear.

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