PseudoLife-MCP

Official

by Pseudogiant-xr

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

memory_outcome

Record whether a task succeeded, failed, or was corrected, so the system distils it into lessons for future sessions.

Instructions

Record a procedural outcome — what worked, failed, or was corrected. The dream distils signals into next session's lessons.

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

TableJSON 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. Credits this session's searches from the last hour; log before that lapses.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.7/5.0

Behavior4/5

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

Annotations already declare the write/non-idempotent/non-destructive profile, so the description's added value is the Postgres dependency ('needs Postgres'), the credit mechanism for used_ids, and the one-hour expiry window. It also explains the used_ids_* result buckets, which clarifies what a partial or failed attribution looks like. It stops short of stating permissions or failure behavior beyond the used_ids_errors bucket.

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?

The purpose is front-loaded in the first sentence, followed by dependency and return information. The long used_ids_* enumeration is informative but dense and partly duplicates the output schema, slightly bloating the definition.

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 an output schema, the description covers purpose, environment dependency, the credit/timing constraint, and partial-failure semantics. Nothing critical is missing, though the relationship to sibling memory tools is unstated.

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 every parameter is already documented, including used_ids, about, detail, and polarity. The description mostly restates the used_ids semantics ('the relevance label only you can write', 'at most 50', last-hour crediting) rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

The description gives a specific verb+resource ('Record a procedural outcome') and enumerates the recorded outcome kinds (worked, failed, corrected). It is clearly distinguishable from storage siblings like memory_store or memory_message in substance, though it never names an alternative to route against.

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?

Usage is implied by 'what worked, failed, or was corrected' and by the instruction to log used_ids 'before that lapses' (a one-hour window), which is genuinely actionable timing guidance. However, there is no explicit when-to-use/when-not statement and no named alternative among the many memory_* siblings.

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