Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_sessions

Establish agent session boundaries and track multi-turn workflows with start, end, list, and bootstrap actions. Returns session records or context snapshots.

Instructions

Manage agent tracking sessions and multi-turn workflow attribution (actions: start, end, list, bootstrap). Use manage_sessions instead of manage_tasks when establishing agent session boundaries and tracking multi-turn workflows rather than individual work items.

Returns session record, bootstrap context snapshot, or active session listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of sessions to list (1-1000).
actionYesThe session management action to execute: start, end, list, bootstrap.
projectNoTarget project name or slug.
agent_idNoAgent identifier for session tracking and change attribution.
metadataNoArbitrary session metadata.
session_idNoUnique session identifier for end.
task_limitNoMaximum runnable tasks to return on bootstrap.
active_onlyNoWhether to return only active unclosed sessions on list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The session management action to execute."New value: +"The session management action to execute: start, end, list, bootstrap."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "start",
+  "end",
+  "list",
+  "bootstrap"
+]
  2. Changed4 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • removedInput schema / properties / metadata / additionalProperties
      Removed value: -{}
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  3. Addedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare write (readOnlyHint=false), non-destructive, non-idempotent. The description adds the return shapes (session record, bootstrap context snapshot, active session listing), which is useful context. However it does not disclose what 'end' does to state, permission needs, or idempotency behavior, so it stays at baseline-plus.

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?

Three compact sentences, front-loaded with purpose and action list, then routing, then returns. No filler, though the parenthetical action list and schema already overlap slightly.

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 multi-action, 8-parameter tool with no output schema, the description covers purpose, action set, sibling routing, and return shapes. It is largely complete, though the destructive semantics of 'end' and per-action prerequisites remain 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 all eight parameters (including limit, active_only, session_id scope, task_limit) are already documented in the schema. The description adds no parameter-level meaning beyond that, 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?

The description states a specific verb+resource (manage agent tracking sessions / multi-turn workflow attribution), enumerates the four actions (start, end, list, bootstrap), and explicitly contrasts itself with the sibling manage_tasks. An agent can distinguish this from manage_tasks without opening 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?

It gives explicit routing: 'Use manage_sessions instead of manage_tasks when establishing agent session boundaries and tracking multi-turn workflows rather than individual work items.' That names the alternative and the deciding condition, but it offers no guidance on choosing among its own actions (start vs. bootstrap vs. list) or other siblings.

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

Deploy Server

Other Tools