PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_outcome

Record what worked, failed, or was corrected to turn session outcomes into next-session lessons and credit used search IDs.

Instructions

Record a procedural outcome — what worked, failed, or was corrected. The dream distils signals into next session's lessons. used_ids credits this session's searches from the last hour; log before that lapses.

Returns {recorded, signal_id, task, outcome}; needs Postgres. used_ids adds used_ids_recorded (credited), used_ids_unmatched (nothing served it), used_ids_served_elsewhere (another session did), used_ids_ignored (not ids), used_ids_truncated (over 50), used_ids_errors (write failed), used_ids_reason (why none landed).

Input Schema

Name	Required	Description
`task`	Yes	Kind of task, in stable wording ("deploy engine to host") so signals for the same work group.
`about`	No	The tool or approach concerned; aids traversal.
`detail`	No	What worked, or what the dead-end was.
`episode`	No	Episode handle for attribution.
`outcome`	Yes	What happened.
`polarity`	No	"+" do-this or "-" avoid; usually omit — it is inferred from the outcome.
`used_ids`	No	Ids of the search hits you actually used, e.g. [1421, 903] — the relevance label only you can write. At most 50.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.18.1Oct 14, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / polarity / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "+",
+      "-"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / used_ids / description

Previous value: -"Ids of the search hits you actually used, e.g. [1421, 903] — the relevance label only you can write. At most 50. Credits this session's searches from the last hour; log before that lapses."New value: +"Ids of the search hits you actually used, e.g. [1421, 903] — the relevance label only you can write. At most 50."

Changed1 schema field changedv0.16.0Oct 3, 2026

addedInput schema / properties / used_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Ids of the search hits you actually used, e.g. [1421, 903] — the relevance label only you can write. At most 50. Credits this session's searches from the last hour; log before that lapses.",
+  "title": "Used Ids"
+}

Changed6 schema fields changedv0.15.0Sep 3, 2026

addedInput schema / properties / about / description

Added value: +"The tool or approach concerned; aids traversal."

addedInput schema / properties / detail / description

Added value: +"What worked, or what the dead-end was."

addedInput schema / properties / episode / description
```
Added value: +"Episode handle for attribution."
```
addedInput schema / properties / outcome / description
```
Added value: +"What happened."
```

addedInput schema / properties / polarity / description

Added value: +"\"+\" do-this or \"-\" avoid; usually omit — it is inferred from the outcome."

addedInput schema / properties / task / description

Added value: +"Kind of task, in stable wording (\"deploy engine to host\") so signals for the same work group."

First observedv0.11.0Jul 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations establish this is a non-read-only, non-idempotent, non-destructive write, and the description adds substantial context beyond that: it requires Postgres, it feeds a downstream dream/consolidation cycle, and it documents failure/partial modes (used_ids_unmatched, used_ids_served_elsewhere, used_ids_ignored, used_ids_truncated, used_ids_errors). It does not address idempotency — repeated logging of the same outcome presumably creates duplicate signals given idempotentHint=false — which is the one notable gap.

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

Conciseness3/5

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

The purpose is correctly front-loaded, but the final sentence enumerates seven used_ids_* return fields — redundant given that an output schema exists and the description is not required to explain return values. That enumeration bloats the description and dilutes the actionable content.

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

Completeness4/5

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

For a 7-parameter write tool with annotations and a full output schema, the description covers purpose, the DB dependency, the crediting window, and the downstream lesson cycle. The main omission is whether repeated calls are safe/duplicative, which matters given idempotentHint=false.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents every parameter; baseline would be 3. The description goes beyond the schema by explaining the semantics of used_ids (it credits this session's searches, and only those from the last hour) and the downstream meaning of unmatched/served_elsewhere outcomes, adding genuine value over the field text.

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 ("Record") and resource ("procedural outcome") and enumerates the outcome space ("what worked, failed, or was corrected"). The phrase "signals into next session's lessons" and the used_ids crediting make clear this is the outcome/lesson-logging tool rather than the general-purpose memory_store or memory_lesson_search siblings.

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

Usage Guidelines3/5

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

Provides one concrete usage constraint — used_ids only credits searches from the last hour, so "log before that lapses" — which implies a timing window for calling it. But there is no explicit when-to-use-this-vs-alternatives guidance: nothing tells the agent when to pick memory_outcome over memory_store, memory_message, or memory_reinforce.

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