Skip to main content
Glama
EremesNG

Thoth-Mem

by EremesNG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mem_get

Expand a selected memory, summary, observation, or evidence ID from a prior result to retrieve full details; enable history to include predecessor lineage for memory, summary, and observation records.

Instructions

Expand one selected memory, summary, observation, or evidence id returned by a prior tool result. Set history:true to include predecessor lineage for memory, summary, or observation records; evidence ids return evidence without lineage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory, summary, observation, or evidence id returned by a prior tool result.
historyNoSet true to expand predecessor lineage for memory, summary, or observation records; evidence ids have no lineage.
correlation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.5.6
    • removedInput schema / properties / after
      Removed value: -{
-  "description": "Timeline observations after the focus item (default: 5)",
-  "maximum": 20,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / before
      Removed value: -{
-  "description": "Timeline observations before the focus item (default: 5)",
-  "maximum": 20,
-  "minimum": 0,
-  "type": "number"
-}
    • addedInput schema / properties / correlation_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / history
      Added value: +{
+  "description": "Set true to expand predecessor lineage for memory, summary, or observation records; evidence ids have no lineage.",
+  "type": "boolean"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Record ID to retrieve, interpreted according to kind"New value: +"Memory, summary, observation, or evidence id returned by a prior tool result."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"string"
    • removedInput schema / properties / include_timeline
      Removed value: -{
-  "description": "Include surrounding observations in the same session",
-  "type": "boolean"
-}
    • removedInput schema / properties / kind
      Removed value: -{
-  "description": "Memory kind to retrieve (defaults to observation)",
-  "enum": [
-    "observation",
-    "prompt"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / max_length
      Removed value: -{
-  "description": "Max characters to return (default: 50000)",
-  "minimum": 100,
-  "type": "number"
-}
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Character offset for large content (default: 0)",
-  "minimum": 0,
-  "type": "number"
-}
  2. Addedv0.4.13
  3. Removedv0.4.1
  4. First observedv0.3.7

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the conditional lineage behavior of history:true and the fact that evidence ids have no lineage, but says nothing about read-only safety, permissions, or what 'expand' actually returns (full record vs. fields).

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 tight sentences with no filler; the core action and its precondition come first, and the second sentence earns its place by covering the history/evidence edge case.

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?

For a read tool with no annotations and no output schema, the description should at minimum say what 'expand' returns and how lineage is presented. It covers the input side adequately but leaves the response shape and correlation_id unexplained.

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 coverage is 67% and both id and history are already documented in the schema; the description largely restates those semantics (id from prior result, history for lineage) rather than adding syntax or format detail. The undocumented correlation_id is not covered anywhere.

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 a specific verb ('Expand') and a precise resource (one memory/summary/observation/evidence id), and the phrase 'returned by a prior tool result' distinguishes it from search-style siblings like mem_recall or mem_context. It does not name an alternative sibling explicitly, so it falls short of full differentiation.

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 precondition for use is clear: you must already hold an id produced by a prior tool result, which implicitly routes the agent away from recall/search tools. There are no explicit when-not conditions or named alternatives, but the context is unambiguous.

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