Skip to main content
Glama
timgordontg

engrim

by timgordontg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

engrim_context

Retrieve a project's curated memory pack of key decisions, constraints, and conventions to orient an agent at session start or after context loss.

Instructions

Read-only query: Return this project's curated session-boot memory pack (high-signal architectural decisions, active constraints, and conventions) to orient an agent at the start of a session or after clearing context. Safe to call repeatedly with zero mutations or external side effects. Records are prioritized and truncated to strictly fit within the specified character budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoMaximum character budget for the returned memory pack (default 4000). Prioritizes active decisions and constraints.
projectNoProject identifier tag; 'auto' infers from current working directory repository root.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
charsYes
loadedYes
projectYes
recordsYes
total_activeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Curated session-boot pack within the character budget.",
+  "properties": {
+    "chars": {
+      "type": "integer"
+    },
+    "loaded": {
+      "type": "integer"
+    },
+    "project": {
+      "type": "string"
+    },
+    "records": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_active": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "project",
+    "loaded",
+    "total_active",
+    "chars",
+    "records"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changedv1.4.2
    • changedInput schema / properties / budget / description
      Previous value: -"Character budget for the pack."New value: +"Maximum character budget for the returned memory pack (default 4000). Prioritizes active decisions and constraints."
    • addedInput schema / properties / project / description
      Added value: +"Project identifier tag; 'auto' infers from current working directory repository root."
    • addedInput schema / required
      Added value: +[]
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Despite no annotations, the description transparently declares read-only, zero side effects, and prioritization/truncation behavior. This fully satisfies the disclosure burden for a query tool.

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, front-loaded with the read-only guarantee and the purpose. No filler; each clause serves a distinct role.

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

Completeness5/5

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

Given an output schema exists and the tool is a simple query with two optional parameters, the description covers purpose, safety, and behavior. Nothing essential is missing.

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 covers both parameters (100% coverage), so description adds little beyond what the schema states. It reinforces the budget behavior but does not provide new information.

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 states a specific action ('Return') on a specific resource ('curated session-boot memory pack') and clearly distinguishes from sibling tools by focusing on boot-time orientation. It is unambiguous about what the tool returns and its purpose.

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?

Provides explicit context for when to use: 'at the start of a session or after clearing context.' Does not name alternatives or exclusions, but the use case is clear enough to route an agent appropriately.

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