Skip to main content
Glama
worakorn-prince

th-memory-mcp

by worakorn-prince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Recent interactions

get_recent_interactions

Retrieve recently captured raw interactions, optionally filtered by kind or session, to audit history or prepare for memory distillation.

Instructions

List recently captured raw interactions (newest first) as [id] ts [kind] content lines. Optionally filter by kind. Use for auditing history or before distilling memory.

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by kind (prompt / tool_call / error)
limitNoMax rows (default 20, max 100)
sessionIdNoFilter by captured session id (default: all sessions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.0
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Filter by captured session id (default: all sessions)",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observedv2.2.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results are newest first and formatted as '[id] ts [kind] content lines', but does not explicitly state read-only behavior, pagination semantics beyond the schema's limit, or any authorization constraints.

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 compact sentences, front-loads the main action and output shape, then gives usage context. Every sentence earns its place with no wasted text.

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?

With no output schema, the description usefully explains the returned line format and ordering. All parameters are covered by the schema, and no required parameters exist. It is nearly complete, though it could explicitly frame the operation as read-only and clarify session filtering behavior.

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%, so all three parameters are already documented in the schema. The description repeats the optional kind filter but adds no additional parameter semantics beyond what the schema provides, making the baseline 3 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?

The description uses a clear verb and resource: 'List recently captured raw interactions' with ordering and output format. It does not explicitly differentiate itself from the sibling search_history tool, though 'raw interactions' and 'before distilling memory' imply a distinct audit/log 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?

It gives clear usage context: 'Use for auditing history or before distilling memory.' It does not specify when not to use it or name search_history as an alternative, so it stops short of full routing guidance.

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