GoodMemory

goodmemory_search_index

Fetch a compact index of memory records matching a query, then retrieve details via get_records. Ideal when you need specific records instead of a summary.

Instructions

Advanced recall (past goodmemory_get_context). Progressive GoodMemory recall step 1: fetch a compact recordRef index for a query, then call goodmemory_get_records for detail. Prefer this over goodmemory_get_context when you need specific records rather than a rendered summary.

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": {
      "query": "<query>"
    },
    "name": "goodmemory_search_index"
  }
}

Input Schema

Name	Required	Description
`cwd`	No	Workspace root. Defaults to the current working directory.
`limit`	No
`query`	Yes
`sessionId`	No	Optional host session id for session-scoped recall.
`includeRuntime`	No
`retrievalProfile`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Jul 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so description must disclose behavior. It says output is a compact recordRef index (not full details), implies read-only, but doesn't specify permissions, idempotency, or side effects. Adequate but not thorough.

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?

Three concise sentences front-loaded with purpose. No wasted words, clear structure.

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?

Missing explanation of optional parameters (limit, retrievalProfile, includeRuntime) and output format. Does not fully describe how to chain steps or handle edge cases. Adequate for simple usage but incomplete given 6 parameters and no output schema.

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 coverage is 33% (only 2 of 6 parameters have descriptions). Description adds no parameter-specific meaning beyond mentioning 'query' implicitly. Low compensation for poor schema coverage.

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?

Description explicitly states it fetches a compact recordRef index for a query, part of progressive recall. Distinct from siblings: goodmemory_get_context (rendered summary) and goodmemory_get_records (detail).

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

Usage Guidelines5/5

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

Clear usage context: prefer over goodmemory_get_context when specific records are needed, and it's step 1 followed by goodmemory_get_records. Explicit alternative and workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server