Skip to main content
Glama

Search Nomos Mneme Episodic Memory

nomos_mem_recall
Read-onlyIdempotent

Search institutional memory for prior decisions, patterns, pitfalls, and conventions before editing code; find architectural rationale and workspace guidance by keyword or semantic query.

Instructions

Search Nomos Mneme institutional memory records (decisions, patterns, pitfalls, axioms) matching a keyword or semantic query. Use when retrieving prior architectural rationale, learned pitfalls, or workspace conventions before editing code. Do NOT use when inspecting compiled quality gate rules (use nomos_capabilities instead) or listing open backlog tasks (use nomos_task_dag instead).

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": "nomos_mem_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching memory records to return.
queryYesKeyword or technical phrase to search in Nomos Mneme.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of returned records.
itemsYesMatching Nomos Mneme memory records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data and the description correctly does not restate it. The description adds useful scope context by naming the record taxonomy being searched, but says nothing about ranking, result relevance, or whether an empty match is possible. With annotations carrying the behavioral burden, a 3 is appropriate rather than a 4.

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 sentences, zero filler, with the core purpose front-loaded before the exclusions. Every clause carries routing or scoping information; no restatement of the title or annotations.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and annotations fully cover the safety profile. The description supplies the remaining decision-critical pieces: what corpus is searched, what it contains, and when to pick a sibling instead. Complete for a two-parameter read-only search tool.

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 coverage is 100%, so both parameters are fully documented in the schema and the baseline is 3. The description adds only one nuance beyond the schema: that the query may be a keyword OR a semantic query, while the schema says "keyword or technical phrase" — a small clarification of accepted input form. Limit behavior (default 5, max 50) is left entirely to the schema.

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 opens with a concrete verb+resource: "Search Nomos Mneme institutional memory records," and enumerates the record types (decisions, patterns, pitfalls, axioms) plus the matching modes (keyword or semantic). It also names the two siblings it is not (nomos_capabilities for compiled gate rules, nomos_task_dag for open backlog tasks). An agent can distinguish this from every listed sibling without opening a schema.

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?

It states an explicit when-to-use trigger (retrieving prior architectural rationale, learned pitfalls, or workspace conventions before editing code) and two explicit when-not-to-use cases with named alternatives. Nothing is left to inference about routing.

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