Skip to main content
Glama
Sign In
GoodMemory

GoodMemory

by hjqcan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

goodmemory_get_records

Retrieve memory records by reference IDs to access their detailed content.

Instructions

Advanced recall. Use this for progressive GoodMemory recall after search_index or timeline returns recordRefs that need detail.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recordRefs": "<recordRefs>"
    },
    "name": "goodmemory_get_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorkspace root. Defaults to the current working directory.
sessionIdNoOptional host session id for session-scoped recall.
recordRefsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Advanced recall' without mentioning idempotency, error handling, or access requirements, which is insufficient for a read operation tool.

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 a single, concise sentence that is front-loaded with 'Advanced recall' and provides specific usage context, earning its place with no wasted words.

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?

Given no output schema and three parameters, the description fails to explain what 'detail' is returned, how records are selected, or how it differs from sibling tools like goodmemory_get_context, leaving gaps in completeness.

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 67%, so baseline is 3. The description adds no parameter details beyond the schema; it does not explain recordRefs format or usage, thus providing no extra value.

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

Purpose5/5

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

The description clearly states the tool is for 'Advanced recall' to get details of recordRefs after using search_index or timeline, distinguishing it as a follow-up step for detail retrieval.

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 to use after search_index or timeline returns recordRefs, providing clear context. It names alternative tools for the preceding steps, though it lacks explicit exclusions for sibling tools like goodmemory_get_context.

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