PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_episode_start

Opens a named sub-episode to group related memories under a task title for episode-scoped search. Call to nest work inside the session episode; end returns to parent.

Instructions

Open a named sub-episode; it nests under the session episode, and memories stored while it is open carry its id + title for episode-scoped search. memory_episode_end closes it and pops back.

Input Schema

TableJSON Schema

Name	Required	Description
`hint`	No	Optional note on what the task is about.
`title`	Yes	Short name for the task, used in later recaps.
`episode`	No	Your session handle (from the session-start briefing) — anchors the sub-episode to YOUR session when several run concurrently.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.15.0Sep 3, 2026

addedInput schema / properties / episode

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Your session handle (from the session-start briefing) — anchors the sub-episode to YOUR session when several run concurrently.",
+  "title": "Episode"
+}

addedInput schema / properties / hint / description

Added value: +"Optional note on what the task is about."

addedInput schema / properties / title / description

Added value: +"Short name for the task, used in later recaps."

First observedv0.11.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare the write/idempotency profile (readOnlyHint=false, idempotentHint=false); the description goes beyond them by disclosing the nesting/stacking semantics and the side effect that memories written while open carry the episode id + title. It omits auth or concurrency caveats beyond the reference to several sessions running concurrently.

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?

Two tight sentences with zero filler. The core action and the nesting relationship are front-loaded, and the closing counterpart is mentioned last as a natural follow-on.

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?

An output schema exists, so return values need not be explained. The description adequately covers the state transition and scoping effect for a stateful episode tool, leaving only minor gaps such as what happens on nested or repeated opens.

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 the schema already documents title, hint, and episode (session handle). The description adds no format or syntax detail beyond what the schema provides, so the baseline of 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 ('Open a named sub-episode') and immediately clarifies the containment model (nests under the session episode). It also names the sibling that undoes it ('memory_episode_end closes it and pops back'), so an agent can distinguish the pair without reading either 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?

The description explains the condition for use: memories stored while the episode is open get tagged with its id and title for episode-scoped search, which implies you open one before storing related memories. It names the closing complement, but does not explicitly contrast against other ways of scoping memories (e.g. memory_store alone).

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