Skip to main content
Glama
worakorn-prince

th-memory-mcp

by worakorn-prince
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search prompt history

search_history

Find past user prompts by keyword and return timestamped snippets for reviewing prior interactions. Optionally filter results by session to focus on a specific conversation.

Instructions

Search past user prompts (kind='prompt') by keyword. Returns timestamped snippets truncated to 200 chars each.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesText to search in past prompts
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

B3.4/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 behavioral disclosure burden. It usefully states the return format (timestamped snippets truncated to 200 chars), but does not cover permissions, rate limits, pagination, or scope beyond the basic search behavior.

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 with the core purpose front-loaded and no wasted wording. It is appropriately sized for a simple search tool.

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?

For a low-complexity read-only search tool with a fully documented schema, the description is nearly complete: it explains the search scope and result format. The main missing element is explicit guidance about when to use this tool versus related memory retrieval siblings.

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 the parameters already documented in the schema do not need repeating. The description adds minor context about keyword searching and result truncation, but does not provide meaningful additional semantics for query, limit, or sessionId beyond the schema.

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 states a specific verb and resource: search past user prompts by keyword, scoped to kind='prompt'. It is clear what the tool does, though it does not explicitly differentiate from siblings such as recall or get_recent_interactions.

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

Usage Guidelines2/5

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

The description implies the tool is used for keyword searching of past prompts, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say when another sibling tool would be more appropriate.

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