Skip to main content
Glama
PseudoLife-MCP

PseudoLife-MCP

Official

memory_lesson_search

Read-only

Search learned lessons by similarity to the current task to recall what worked, what to avoid, and past corrections before starting work.

Instructions

Search learned lessons (procedural memory) by similarity to the task at hand. Call at the START of a task: what worked, what to avoid, what the user corrected before. Heed polarity - entries — known dead-ends. A lesson describes the run it came from, not this one: apply it where today's specifics match, or it anchors you on a stale framing — re_verify: true marks one whose subject facts have changed since, so re-derive that one.

Returns: {count, entries: [{task, aspect, lesson, about, polarity, outcome, confidence, score, re_verify, re_verify_reason}]}.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe task at hand, described the way it would have been logged.
top_kNoMax entries returned; positive integer. Omit to use memory.lessons.top_k (default 5).
verboseNoFull provenance metadata; default entries are compact.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.22.0
    • changedInput schema / properties / top_k / default
      Previous value: -5New value: +null
    • changedInput schema / properties / top_k / description
      Previous value: -"Max entries returned; positive integer."New value: +"Max entries returned; positive integer. Omit to use memory.lessons.top_k (default 5)."
  2. Changed3 schema fields changedv0.18.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / top_k / description
      Previous value: -"Max entries returned."New value: +"Max entries returned; positive integer."
    • addedInput schema / properties / top_k / minimum
      Added value: +1
  3. Changed3 schema fields changedv0.15.0
    • addedInput schema / properties / query / description
      Added value: +"The task at hand, described the way it would have been logged."
    • addedInput schema / properties / top_k / description
      Added value: +"Max entries returned."
    • addedInput schema / properties / verbose / description
      Added value: +"Full provenance metadata; default entries are compact."
  4. First observedv0.11.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavioral context: that each lesson describes its original run rather than the current one, that it can anchor on stale framing, and that re_verify: true flags facts that have changed. This is real decision-relevant caveat content, not a restatement of hints; only the trailing return-shape listing is redundant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and the when-to-call trigger before the caveats, and every caution sentence carries operational weight. The enumerated return field list is partly wasted since an output schema exists, costing it the top score.

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?

For a read-only similarity search with a full output schema and 100% schema coverage, the description supplies everything an agent needs: when to call, how to interpret polarity and re_verify, and the risk of over-applying a lesson. No material gap remains.

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 query, top_k, and verbose are already fully documented in the schema, including the top_k default fallback. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("Search learned lessons") and immediately narrows the scope with "(procedural memory) by similarity to the task at hand," which cleanly separates it from the declarative-memory siblings like memory_search, memory_fact_get, and memory_world_search. An agent can identify what this returns without opening the schema.

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?

Gives explicit timing ("Call at the START of a task") plus concrete interpretation rules — heed polarity ``-`` entries, apply only where today's specifics match. It stops short of naming an explicit alternative tool or a when-not-to-use condition versus memory_search/memory_recall, so it lands just below the top band.

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