PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_episode_start

Open a named sub-episode under the current session to group memories by task; stored memories carry the episode ID and title for scoped search.

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?

With no annotations, the description carries the burden of behavioral disclosure. It states that the operation is stateful, nests under the session episode, attaches id/title to memories stored while open, and that memory_episode_end pops back. It leaves some edge behavior implicit, such as repeated starts while a sub-episode is already open, but the core side effects are clearly disclosed.

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?

The description is two compact sentences that front-load the purpose and then give the lifecycle and close behavior. Every clause earns its place; there is no filler, repetition, or redundant per-parameter prose.

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 stateful scoping tool with a complete schema and an output schema, the description covers the operation, the reason to use it, and the complementary end call. The only omissions are edge-case behaviors such as what happens if no session episode exists or if called when a sub-episode is already open, which would push it to full completeness.

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 input schema already documents title, hint, and episode. The description only reinforces that title is carried by stored memories and adds no new parameter semantics. Baseline 3 is appropriate here.

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?

Description uses an active verb ('Open') with a clear resource ('a named sub-episode') and explains that it nests under the session episode. It also distinguishes itself from the sibling close/summary/session-title tools by describing the episode-scoped storage effect. An agent can tell at a glance what this tool is for.

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 gives a clear use context: open a sub-episode when you want subsequently stored memories to carry its id + title for episode-scoped search. It names the paired closing tool, memory_episode_end, but does not explicitly list when-not-to-use or alternatives, so it stops just short of full guidance.

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