PseudoLife-MCP

Official

Overview Schema Source Related Servers Discussions Admin

memory_agents

Coordinate agent sessions on the shared board: list peers and leases, update your own status or park, claim/release shared resources. List before shared work and on resume. idle_omitted counts idle peers.

Instructions

update: omitted fields stay. A status update with no park fields clears any park, and its result's warning says so. Park when you stop (park_reason, park_needs, park_clear_by, park_resume); done means no follow-up expected. Automatic wake needs a live listener; otherwise mail waits for your next turn.

claim/release: one selector - lease (coordinator: or claim:), or worktree+path (local shim), or repository_id+path (HTTP). Reclaim renews; a busy lease queues you. File claims are advisory, not edit locks; no globs or directories.

Input Schema

Name	Required	Description	Default
`name`	No	update: the name the board shows for you, up to 120 chars; it overrides your harness's title. "" clears yours.
`path`	No	claim/release: one file relative to worktree/repository_id, up to 4096 chars; no globs or directories.
`task`	No	list/update: current task, up to 120 chars.
`lease`	No	claim/release: coordinator:<project> or claim:<path>, up to 120 chars. Omit with file selectors.
`action`	No	list (default), update, claim or release; pass only that action's fields.	list
`expect`	No	update/claim: expected duration in seconds, integer 1..604800; marks overdue, not a timer or lease TTL.
`status`	No	update: progress; claim: lease purpose. Up to 240 chars. On update, clears any park unless park fields are given.
`project`	No	list/update: project name, up to 120 chars; relevance only.
`children`	No	update: at most 8 distinct nonempty labels, each up to 40 chars. [] clears manual labels; automatic children remain.
`worktree`	No	claim/release, local shim only: absolute Git worktree path, up to 4096 chars; requires path, excludes lease/repository_id.
`park_needs`	No	update: what would unblock you, up to 120 chars; senders use clears only when their message satisfies this need.
`park_reason`	No	update: done, blocked, needs_approval, needs_info, needs_resource or waiting_peer. Empty string clears; null/omitted sends no reason.
`park_resume`	No	update: what to do once cleared, up to 240 chars.
`park_expires`	No	update: positive finite Unix epoch seconds, at most now + 7 days; new parks default to now + 12 hours, refinements keep expiry.
`park_clear_by`	No	update: who may wake this park: exact agent ID, maintainer, anyone, or a supported lease name; up to 120 chars.
`repository_id`	No	claim/release, HTTP: prepared 64-char lowercase SHA-256 repository ID; requires path, excludes lease/worktree.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.18.3Oct 22, 2026

changedInput schema / properties / park_reason / anyOf

Previous value: -[
-  {
-    "maxLength": 20,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "done",
+      "blocked",
+      "needs_approval",
+      "needs_info",
+      "needs_resource",
+      "waiting_peer",
+      ""
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / park_reason / description

Previous value: -"update: done, blocked, needs_approval, needs_info, needs_resource or waiting_peer (max 20 chars). Empty string clears; null/omitted sends no reason."New value: +"update: done, blocked, needs_approval, needs_info, needs_resource or waiting_peer. Empty string clears; null/omitted sends no reason."

Changed17 schema fields changedv0.18.1Oct 14, 2026

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

addedInput schema / properties / action / description

Added value: +"list (default), update, claim or release; pass only that action's fields."

addedInput schema / properties / children / description

Added value: +"update: at most 8 distinct nonempty labels, each up to 40 chars. [] clears manual labels; automatic children remain."

addedInput schema / properties / expect / description

Added value: +"update/claim: expected duration in seconds, integer 1..604800; marks overdue, not a timer or lease TTL."

addedInput schema / properties / lease / description

Added value: +"claim/release: coordinator:<project> or claim:<path>, up to 120 chars. Omit with file selectors."

addedInput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 120,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "update: the name the board shows for you, up to 120 chars; it overrides your harness's title. \"\" clears yours.",
+  "title": "Name"
+}

addedInput schema / properties / park_clear_by / description

Added value: +"update: who may wake this park: exact agent ID, maintainer, anyone, or a supported lease name; up to 120 chars."

addedInput schema / properties / park_expires / description

Added value: +"update: positive finite Unix epoch seconds, at most now + 7 days; new parks default to now + 12 hours, refinements keep expiry."

addedInput schema / properties / park_needs / description

Added value: +"update: what would unblock you, up to 120 chars; senders use clears only when their message satisfies this need."

addedInput schema / properties / park_reason / description

Added value: +"update: done, blocked, needs_approval, needs_info, needs_resource or waiting_peer (max 20 chars). Empty string clears; null/omitted sends no reason."

addedInput schema / properties / park_resume / description

Added value: +"update: what to do once cleared, up to 240 chars."

addedInput schema / properties / path / description

Added value: +"claim/release: one file relative to worktree/repository_id, up to 4096 chars; no globs or directories."

addedInput schema / properties / project / description

Added value: +"list/update: project name, up to 120 chars; relevance only."

addedInput schema / properties / repository_id / description

Added value: +"claim/release, HTTP: prepared 64-char lowercase SHA-256 repository ID; requires path, excludes lease/worktree."

addedInput schema / properties / status / description

Added value: +"update: progress; claim: lease purpose. Up to 240 chars. On update, clears any park unless park fields are given."

addedInput schema / properties / task / description

Added value: +"list/update: current task, up to 120 chars."

addedInput schema / properties / worktree / description

Added value: +"claim/release, local shim only: absolute Git worktree path, up to 4096 chars; requires path, excludes lease/repository_id."

Addedv0.16.0Oct 3, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that board writes require an authenticated adapter, that status/parks grant no approval, that file claims are advisory rather than edit locks, that automatic wake needs a live listener or mail waits a turn, and that reclaim renews while a busy lease queues you. It also spells out the non-obvious side effect that a status update without park fields clears any park and surfaces a warning.

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?

Front-loads purpose, then groups guidance by action (list, update, claim/release), which matches how an agent will scan it. The telegraphic, fragment-heavy style compresses 16 parameters into little space, but a few clauses ("idle_omitted counts idle peers") are too terse to parse on first read.

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 documented, and the description covers the high-risk gaps for a 4-action, 16-param tool: auth requirement, advisory nature of claims, wake/listener caveat, park defaults and expiry behavior. Only the list/update scoping of project/task relevance is left implicit.

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 coverage is 100%, so baseline is 3; the description still adds cross-parameter semantics the schema cannot express per-field — mutually exclusive selector forms (lease vs worktree+path vs repository_id+path), 'omitted fields stay' on update, and park-clearing behavior. cryptic fragment like "idle_omitted counts idle peers" is unexplained and adds little.

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 opening sentence names the resource (agent sessions on the shared board) and enumerates the four verbs (list, update, claim, release), so an agent can tell what it does without opening the schema. It never names a sibling, but no sibling in the list covers leases/board coordination, so ambiguity is low.

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?

"List before shared work and on resume" and "Park when you stop ... done means no follow-up expected" give concrete triggering conditions for two of the four actions. Claim/release selection is also guided by the one-selector rule. It lacks explicit when-not/alternative-tool routing, keeping it below a 5.

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