Skip to main content
Glama
Sign In

Engram

by tools.engram
OverviewDiscussionsAdmin

Start Engram

engram_start

Begin meaningful work in a repository with a Markdown briefing: session id, ranked private/public memory, workspace guidance and optional checklists. Unlike engram_smarter, this includes workspace onboarding/activation guidance; unlike engram_rehydrate, it prepares a starting briefing instead of reconstructing a prior journal. Use once when beginning work; choose engram_smarter for a task switch and engram_rehydrate for recovery.

Supply repo and task when known; context overrides the generated project/market/role/stack/task query. Reuses one eligible active journal; new_session=true deliberately creates a separate journal. Supply session_id for parallel work. Ambiguous automatic selection returns 409; list sessions and choose an exact id. Records a session event; repeating may add events or open another session. Consumes workspace daily call quota; quota exhaustion requires reset or a plan change, not immediate retries. OAuth: memory:read and session:write.

Input Schema

NameRequiredDescriptionDefault
repoNoRepository slug, e.g. engram or billing-api, within the authenticated workspace. This is a memory filter, not a filesystem path or workspace selector.
roleNoAgent responsibility used in task context, e.g. backend engineer. Start/setup default to implementation agent.
taskNoConcrete current goal or decision, e.g. diagnose checkout retries; used to focus context and session recovery.
depthNoDefault focused uses a small retrieval budget; deep expands it when focused results are insufficient. An explicit limit overrides the default budget.
limitNoMaximum retrieved memories, 1–30. Omitted defaults: focused=8, deep=16; explicit values override these defaults.
stackNoProject technologies used to focus context; omit when unknown.
marketNoBusiness/domain context, e.g. fintech or education; not a geographic access setting.
contextNoOptional full task context; overrides the query generated from project, role, market, stack and task.
projectNoProduct/project name for session context. Start/setup use it as the repository hint when repo is omitted.
agent_toolNoCalling client name for attribution, e.g. codex, claude-code, cursor, or gemini. Omit if unknown.
session_idNoExact journal id from start/rehydrate/list_sessions. Disambiguates parallel work; writing requires your active session. Rehydrate may read shared or closed history.
new_sessionNoDefault false reuses one eligible active journal. True creates a separate journal for parallel work; retries can create another session. Keep the returned session_id.
include_skillsNoInclude relevant procedural checklists. If omitted, the server infers this from task/context keywords; false suppresses checklists.

Output Schema

NameRequiredDescriptionDefault
textYesThe same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool.
formatYesPayload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text.
truncatedYesTrue when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / new_session
      Added value: +{
+  "description": "Default false reuses one eligible active journal. True creates a separate journal for parallel work; retries can create another session. Keep the returned session_id.",
+  "type": "boolean"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Exact journal id from start/rehydrate/list_sessions. Disambiguates parallel work; writing requires your active session. Rehydrate may read shared or closed history.",
+  "type": "string"
+}
  2. Changed13 schema fields changed
    • addedInput schema / properties / agent_tool / description
      Added value: +"Calling client name for attribution, e.g. codex, claude-code, cursor, or gemini. Omit if unknown."
    • addedInput schema / properties / context / description
      Added value: +"Optional full task context; overrides the query generated from project, role, market, stack and task."
    • addedInput schema / properties / depth / description
      Added value: +"Default focused uses a small retrieval budget; deep expands it when focused results are insufficient. An explicit limit overrides the default budget."
    • addedInput schema / properties / include_skills / description
      Added value: +"Include relevant procedural checklists. If omitted, the server infers this from task/context keywords; false suppresses checklists."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum retrieved memories, 1–30. Omitted defaults: focused=8, deep=16; explicit values override these defaults."
    • addedInput schema / properties / market / description
      Added value: +"Business/domain context, e.g. fintech or education; not a geographic access setting."
    • addedInput schema / properties / project / description
      Added value: +"Product/project name for session context. Start/setup use it as the repository hint when repo is omitted."
    • addedInput schema / properties / repo / description
      Added value: +"Repository slug, e.g. engram or billing-api, within the authenticated workspace. This is a memory filter, not a filesystem path or workspace selector."
    • addedInput schema / properties / role / description
      Added value: +"Agent responsibility used in task context, e.g. backend engineer. Start/setup default to implementation agent."
    • addedInput schema / properties / stack / description
      Added value: +"Project technologies used to focus context; omit when unknown."
    • addedInput schema / properties / stack / items / description
      Added value: +"Technology name, e.g. TypeScript or PostgreSQL."
    • addedInput schema / properties / task / description
      Added value: +"Concrete current goal or decision, e.g. diagnose checkout retries; used to focus context and session recovery."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "format": {
+      "description": "Payload encoding: Markdown context/checkpoint, serialized JSON data, or plain confirmation text.",
+      "enum": [
+        "markdown",
+        "json",
+        "text"
+      ],
+      "type": "string"
+    },
+    "text": {
+      "description": "The same bounded payload as content[0].text; interpret it using format. JSON text contains the endpoint-specific fields described by this tool.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when the payload exceeded 120,000 characters and was cut with a notice. Narrow the request; truncated JSON is not parseable.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "text",
+    "format",
+    "truncated"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations (which only say non-readonly, non-destructive, non-idempotent, closed-world): it discloses that a session event is recorded and repeats may add events or open another session, that it consumes a workspace daily call quota whose exhaustion requires a reset/plan change rather than retries, the required OAuth scopes (memory:read, session:write), and the 409 ambiguity outcome.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and sibling differentiation before dense operational detail. Three paragraphs for a 13-parameter tool is proportionate, and each sentence (quota, OAuth, 409, session reuse) carries distinct information; density is high but not padded.

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?

With an output schema present, return values need no explanation, and the description still covers the substantive gaps an agent faces: auth scopes, quota limits, non-idempotent session-event recording, 409 ambiguity handling, and the context-override precedence. Nothing needed to invoke it correctly appears missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds interaction semantics the schema lists only in isolation: context overrides the generated project/market/role/stack/task query, new_session=true deliberately opens a separate journal versus default reuse of one eligible active journal, and session_id disambiguates parallel work. This is more than restatement, though a fair amount still duplicates the schema prose.

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?

States a specific verb ('Begin meaningful work') plus resource ('repository') and enumerates the payload (session id, ranked private/public memory, workspace guidance, optional checklists). It also explicitly names and contrasts two siblings — engram_smarter (task switch) and engram_rehydrate (recovery) — so an agent can disambiguate without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Use once when beginning work'), names both alternatives with their selecting conditions, and adds edge-case routing: supply session_id for parallel work, use list_sessions and pick an exact id when automatic selection returns 409, and new_session=true for a deliberately separate journal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Engram toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources