PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_session_title

Set a custom title for the current session episode. Call at the start of work to replace generic titles, ensuring session recaps are meaningful; can rename anytime.

Instructions

Name THIS session's auto-opened episode (default titles are generic). Call once at the start of work so session recaps read meaningfully. Idempotent; call again to rename.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes	What this session is about, e.g. "Pseudolife-MCP" or "auth-refactor".
`episode`	No	Your session handle — names that session's root directly (the identity a hook-registered client has).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.15.0Sep 3, 2026

addedInput schema / properties / episode

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Your session handle — names that session's root directly (the identity a hook-registered client has).",
+  "title": "Episode"
+}

addedInput schema / properties / title / description

Added value: +"What this session is about, e.g. \"Pseudolife-MCP\" or \"auth-refactor\"."

First observedv0.11.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does so by disclosing idempotency, renamability, and the effect on session recaps. It could add more detail about whether a custom title fully replaces the prior one or how the episode handle is resolved, but the core behavior is clear.

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?

Three short sentences, all informative, with no fluff. The action and timing are front-loaded, and the idempotency is stated compactly without repetition.

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?

Complete for a simple setter: it covers when to call, repeat-call behavior, and why it matters. The optional episode parameter and output schema fill remaining context, so nothing critical is missing.

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 explains title and episode well; the description only adds usage context, not param-level detail. Baseline 3 is appropriate because the schema does the heavy lifting.

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?

The description uses a specific imperative ('Name THIS session's auto-opened episode'), identifies the object being modified, and contrasts with generic defaults. It clearly differentiates from siblings like memory_episode_summary or memory_episode_start by targeting the session title specifically.

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

Usage Guidelines5/5

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

Explicitly says to call once at the start of work and that calling again renames, giving both timing and repeat behavior. It also explains why the call matters ('so session recaps read meaningfully'), which helps an agent decide when the tool is relevant.

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