Skip to main content
Glama
EremesNG

Thoth-Mem

by EremesNG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mem_project

Inspect project memory without changing it: list aliases, view timelines, briefings, summaries, observations, and history for a project or session.

Instructions

Inspect project views without mutation. action="list": no fields required. action="timeline": project_key required; optionally since, until, cursor, limit, and budget_chars. action="briefing", "summaries", or "observations": project_key required; optionally supply both root_session_key and harness to select that session's summaries/observations (briefing still includes project-wide memories). action="history": id required from a prior result. temporal filters summaries/observations, not timeline. list returns at most 256 exact aliases per project plus aliasCount and aliasesTruncated metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRequired for action="history"; send a record id returned by a prior tool result.
limitNoMaximum items (1-100) for action="timeline" or "observations".
sinceNoOptional inclusive lower ISO-8601 instant for action="timeline" only; must be <= until.
stateNoOptional state filter for action="observations".
untilNoOptional inclusive upper ISO-8601 instant for action="timeline" only; must be >= since.
actionYesInspect project views without mutation. action="list": no fields required. action="timeline": project_key required; optionally since, until, cursor, limit, and budget_chars. action="briefing", "summaries", or "observations": project_key required; optionally supply both root_session_key and harness to select that session's summaries/observations (briefing still includes project-wide memories). action="history": id required from a prior result. temporal filters summaries/observations, not timeline. list returns at most 256 exact aliases per project plus aliasCount and aliasesTruncated metadata.
cursorNoUnchanged nextCursor from a prior mem_project action="timeline" result; keep project_key, since, and until unchanged.
harnessNoNative harness for the optional root_session_key filter; supply both or omit both. Not accepted for action="timeline".
temporalNoFilter summaries/observations: current selects current summary versions or observation correction-chain leaves; history includes older summary versions or selects observation predecessors. Not accepted for action="timeline".
project_keyNoExact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content. Required for action="timeline", "briefing", "summaries", or "observations"; not required for "list" or "history".
budget_charsNoOptional aggregate character budget for timeline, briefing, summaries, or observations; timeline clamps a positive integer to 1024-20000 characters.
root_session_keyNoOptional session filter for action="briefing", "summaries", or "observations"; supply with harness or omit both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv0.5.6
    • changedInput schema / properties / action / description
      Previous value: -"Project view to return"New value: +"Inspect project views without mutation. action=\"list\": no fields required. action=\"timeline\": project_key required; optionally since, until, cursor, limit, and budget_chars. action=\"briefing\", \"summaries\", or \"observations\": project_key required; optionally supply both root_session_key and harness to select that session's summaries/observations (briefing still includes project-wide memories). action=\"history\": id required from a prior result. temporal filters summaries/observations, not timeline. list returns at most 256 exact aliases per project plus aliasCount and aliasesTruncated metadata."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "summary",
-  "graph",
-  "topics",
-  "topic",
-  "health"
-]New value: +[
+  "list",
+  "timeline",
+  "briefing",
+  "history",
+  "summaries",
+  "observations"
+]
    • addedInput schema / properties / budget_chars
      Added value: +{
+  "description": "Optional aggregate character budget for timeline, briefing, summaries, or observations; timeline clamps a positive integer to 1024-20000 characters.",
+  "type": "number"
+}
    • removedInput schema / properties / continuation
      Removed value: -{
-  "description": "Opaque continuation token returned by graph navigation views",
-  "type": "string"
-}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Unchanged nextCursor from a prior mem_project action=\"timeline\" result; keep project_key, since, and until unchanged.",
+  "maxLength": 4096,
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / focus_node_id
      Removed value: -{
-  "description": "Graph focus node id for navigation=neighborhood, currently obs:<id>",
-  "type": "string"
-}
    • addedInput schema / properties / harness
      Added value: +{
+  "description": "Native harness for the optional root_session_key filter; supply both or omit both. Not accepted for action=\"timeline\".",
+  "enum": [
+    "opencode",
+    "codex",
+    "claude",
+    "pi",
+    "mcp",
+    "cli",
+    "import"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Required for action=\"history\"; send a record id returned by a prior tool result.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / include_superseded
      Removed value: -{
-  "description": "Explicit history opt-in; honored by navigation=superseded only",
-  "type": "boolean"
-}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum items to return"New value: +"Maximum items (1-100) for action=\"timeline\" or \"observations\"."
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / limit / maximum
      Previous value: -500New value: +100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / max_chars
      Removed value: -{
-  "description": "Response character budget; 0 is supported for action=summary only",
-  "maximum": 20000,
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / navigation
      Removed value: -{
-  "description": "Graph navigation mode for action=graph; defaults to ledger",
-  "enum": [
-    "ledger",
-    "neighborhood",
-    "lineage",
-    "community",
-    "superseded"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / observation_id
      Removed value: -{
-  "description": "Observation id for lineage or superseded graph navigation",
-  "exclusiveMinimum": 0,
-  "maximum": 9007199254740991,
-  "type": "integer"
-}
    • removedInput schema / properties / project
      Removed value: -{
-  "description": "Project name. Required except action=list and optional for action=topics or health",
-  "type": "string"
-}
    • addedInput schema / properties / project_key
      Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content. Required for action=\"timeline\", \"briefing\", \"summaries\", or \"observations\"; not required for \"list\" or \"history\".",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / relation
      Removed value: -{
-  "description": "Graph relation filter for action=graph",
-  "enum": [
-    "HAS_TYPE",
-    "IN_PROJECT",
-    "HAS_TOPIC_KEY",
-    "HAS_WHAT",
-    "HAS_WHY",
-    "HAS_WHERE",
-    "HAS_LEARNED"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / root_session_key
      Added value: +{
+  "description": "Optional session filter for action=\"briefing\", \"summaries\", or \"observations\"; supply with harness or omit both.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional inclusive lower ISO-8601 instant for action=\"timeline\" only; must be <= until.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / state
      Added value: +{
+  "description": "Optional state filter for action=\"observations\".",
+  "enum": [
+    "pending",
+    "accepted",
+    "rejected",
+    "promoted"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / temporal
      Added value: +{
+  "description": "Filter summaries/observations: current selects current summary versions or observation correction-chain leaves; history includes older summary versions or selects observation predecessors. Not accepted for action=\"timeline\".",
+  "enum": [
+    "current",
+    "history"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / topic_key
      Removed value: -{
-  "description": "Topic key for action=topic or graph filtering",
-  "type": "string"
-}
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Optional inclusive upper ISO-8601 instant for action=\"timeline\" only; must be >= since.",
+  "minLength": 1,
+  "type": "string"
+}
  2. Addedv0.4.13
  3. Removedv0.4.1
  4. First observedv0.3.7

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden; it explicitly says 'without mutation' (read-only), documents cursor semantics ('unchanged nextCursor'), and states list returns at most 256 aliases plus aliasCount/aliasesTruncated. It omits permissions, rate limits, and error behavior, so 4.

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 the tool purpose and then action clauses; no filler sentences. Dense for six actions but appropriately sized, so 4.

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 covers action routing and key constraints, but with no output schema it explains return shape only for action='list' and leaves briefing/summaries/observations/history outputs unspecified. Schema 100% coverage offsets parameter gaps, but return transparency remains incomplete, so 3.

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 top-level text repeats the action property description rather than adding new parameter meaning. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Inspect project views without mutation' and enumerates six actions (list, timeline, briefing, summaries, observations, history), which conveys the tool's read-only inspection role. It does not distinguish mem_project from siblings like mem_recall or mem_context, so 4 rather than 5.

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?

Gives action-by-action requirements (project_key required for timeline/briefing/summaries/observations, id for history, optional session filters) and notes temporal filters apply to summaries/observations, not timeline. It lacks when-not-to-use or explicit alternatives, so 4.

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