Skip to main content
Glama
hacksurvivor

pathmark

by hacksurvivor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Recall memory

recall_memory
Read-onlyIdempotent

Retrieve relevant memories by query, IDs, or tags, and surface the exact memory set used. Use before answering to make recall transparent.

Instructions

Transparent recall for any MCP-capable harness. Use this at task start or before answering to show exactly which memories were used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoExact memory IDs from a prior Pathmark context block. Preserves the original visible-recall set.
kindNo
tagsNoOptional tags to scope visible recall, such as the current workspace tag.
limitNo
queryNoTask, repo, or question to retrieve memory for. Empty query returns recent records.
namespaceNo
includeRecordsNoInclude a second, untruncated full-record copy alongside usedMemories. Defaults to false: it duplicates data already in context/usedMemories and is unbounded in size. Set true only when full record bodies are required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.15
    • changedInput schema / properties / includeRecords / description
      Previous value: -"Include a second full-record copy. Defaults to true for compatibility."New value: +"Include a second, untruncated full-record copy alongside usedMemories. Defaults to false: it duplicates data already in context/usedMemories and is unbounded in size. Set true only when full record bodies are required."
  2. Changed2 schema fields changedv0.1.9
    • addedInput schema / properties / ids
      Added value: +{
+  "description": "Exact memory IDs from a prior Pathmark context block. Preserves the original visible-recall set.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 30,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / includeRecords
      Added value: +{
+  "description": "Include a second full-record copy. Defaults to true for compatibility.",
+  "type": "boolean"
+}
  3. Addedv0.1.7

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds 'Transparent recall' and 'show exactly which memories were used', which is more about purpose than behavior. It does not describe rate limits, authentication, or what happens with includeRecords, but given annotations cover safety, the added context is minimal yet non-contradictory.

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 sentences, front-loaded with the core purpose and usage. Every word earns its place, and it avoids redundancy with the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters and no output schema, the description is minimal. It does not explain the return structure (e.g., usedMemories vs includeRecords), how to retrieve memory IDs from prior context, or the interaction between query, tags, and ids. An agent may struggle to formulate correct requests without additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 57%, meaning several parameters (kind, limit, namespace) lack descriptions. The tool description does not explain any parameter semantics, such as how to obtain memory IDs or the meaning of namespace. It fails to compensate for the missing schema details, leaving an agent with incomplete guidance for constructing valid calls.

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 clearly states the tool's purpose: transparent recall showing exactly which memories were used. It distinguishes it from search_memory and other memory tools by emphasizing 'show exactly which memories were used' at task start, which implies a distinct role in surfacing used memories rather than searching or managing them.

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 description explicitly instructs when to use the tool: 'at task start or before answering'. This provides a clear usage context. However, it does not mention alternatives or when not to use it, but the specific timing guidance is strong enough to guide an agent.

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