Skip to main content
Glama
contextstream

ContextStream MCP Server

Session

session
Read-onlyIdempotent

Manage AI session memory: capture decisions and lessons, recall past conversations, and ground context from prior work. Action-driven retrieval and storage for persistent context.

Instructions

Session and memory management — NOT for codebase/file search (use the 'search' tool for that). LESSONS LIVE HERE: when a mistake or correction happens, call action='capture_lesson' (NEVER write lessons to ~/.claude/.../memory/, .cursorrules, or other local markdown — local files are invisible to [LESSONS_WARNING] auto-surfacing on future turns and across sessions). PAST SESSIONS LIVE HERE: use action='recall' FIRST when the user references "last time", "previous", "yesterday", or is continuing prior work — full-text transcripts are indexed across every prior session. context() may surface [GROUNDING]; use action='ground' with user_message for a one-shot bundle (recall + docs + decisions + lessons + skills) outside context(). Actions: capture (save decision/insight), retro_capture (after-the-fact decision/note/snapshot capture from prior work with source provenance — title plus content and/or query/transcript_ids), capture_lesson (mistakes/corrections — title+trigger+impact+prevention), get_lessons (retrieve lessons), update_lesson / delete_lesson (maintain a saved lesson by lesson_id — UUID or lookup text), recall (retrieve past conversation context via ranked fusion of transcripts/snapshots/docs/decisions), ground (one-shot prior-work bundle), remember (quick save), user_context (get preferences), summary (workspace summary), compress (compress chat), delta (changes since timestamp), smart_search (searches MEMORY/conversation history only, not code), decision_trace (trace decision provenance), restore_context (restore state after compaction). Plan actions: capture_plan, get_plan, update_plan, list_plans. Suggested rules actions: list_suggested_rules, suggested_rule_action, suggested_rules_stats. Team actions: team_decisions, team_lessons, team_plans. Team/personal mode: set_account_mode (team|personal|auto).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode metadata for capture/search filtering (e.g., primary/subagent)
tagsNoInput parameter: tags.
agentNoAgent name metadata for capture/search filtering
goalsNoGoals for capture_plan
limitNoMaximum number of results to return.
queryNoQuery for recall/search/lessons/decision_trace
sinceNoISO timestamp for delta
stepsNoImplementation steps for capture_plan
titleNoTitle for capture/capture_lesson/capture_plan
actionYesAction to perform
due_atNoDue date for plan (ISO timestamp)
impactNoWhat went wrong
statusNoPlan status
contentNoContent for capture/remember/compress
node_idNoNode ID (full 36-char UUID)
plan_idNoPlan ID (UUID) or plan title text for get_plan/update_plan; omit to resolve the latest actionable plan
rule_idNoSuggested rule ID for actions
task_idNoTask ID (full 36-char UUID)
triggerNoWhat caused the problem (for capture_lesson), or restore trigger for restore_context
categoryNoInput parameter: category.
event_idNoEvent ID (full 36-char UUID)
keywordsNoKeywords for matching.
severityNoInput parameter: severity.
code_refsNoInput parameter: code refs.
lesson_idNoLesson ID (full 36-char UUID)
event_typeNoEvent type for capture
importanceNoInput parameter: importance.
max_tokensNoMax tokens for summary
preventionNoHow to prevent in future
project_idNoProject ID (UUID).
provenanceNoInput parameter: provenance.
session_idNoSession identifier.
descriptionNoDescription for capture_plan
is_personalNoMark plan as personal (only visible to creator). For capture_plan/list_plans.
rule_actionNoAction to perform on suggested rule
snapshot_idNoSpecific snapshot ID to restore (defaults to most recent)
source_toolNoTool that generated this plan
account_modeNoExecution mode for set_account_mode
user_messageNoNatural-language anchor for action=ground (falls back to query)
workspace_idNoWorkspace ID (UUID).
include_tasksNoInclude tasks when getting plan
max_snapshotsNoNumber of recent snapshots to consider (default: 1)
suggestion_idNoSuggestion ID (full 36-char UUID)
transcript_idNoTranscript ID to use as source evidence for retro_capture
include_impactNoWhether to include impact.
min_confidenceNoMinimum confidence threshold for listing rules
transcript_idsNoTranscript IDs to use as source evidence for retro_capture
include_relatedNoInclude related context.
include_decisionsNoInclude related decisions.
modified_keywordsNoModified keywords when action is modify
modified_instructionNoModified instruction when action is modify
include_durable_contextNoInclude durable snapshots/transcripts/docs/decisions in restore payload (default true)
Behavior1/5

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

The description contradicts annotations: readOnlyHint=true but the tool includes write actions (capture, capture_lesson, remember, etc.), and destructiveHint=false despite delete_lesson and other destructive actions. The description itself is detailed about behaviors, but the contradiction with annotations is severe, reducing transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very long and front-loaded with key distinctions, but it could be more concise by separating action lists into structured bullet points. It is moderately well-structured but verbose.

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?

Given the tool has 52 parameters and many actions, the description covers usage context well (when to use recall, ground, etc.) and explains key concepts. However, it lacks details on return values and error handling, which would be beneficial for such a complex tool.

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 coverage is 100%, so baseline is 3. The description adds context for some parameters (e.g., user_message for ground) but mostly lists actions without deeper parameter details. It does not substantially enhance understanding beyond the schema.

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 clearly states that this tool is for 'Session and memory management' and explicitly distinguishes it from 'search' tool for codebase/file search. It lists many specific actions, making the purpose very clear.

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?

The description provides explicit guidance on when to use actions like 'recall' for past sessions and 'capture_lesson' for mistakes. It warns against writing lessons to local files and explains how to use 'ground' for one-shot bundles. This is thorough and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/contextstream/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server