Skip to main content
Glama
contextstream

ContextStream MCP Server

Initialize conversation session

init

Start a conversation by initializing a session and automatically fetching relevant context, including workspace info, project details, recent memory, and decisions.

Instructions

Initialize a new conversation session and automatically retrieve relevant context. This is the FIRST tool AI assistants should call when starting a conversation. Returns: workspace info, project info, recent memory, recent decisions, relevant context, high-priority lessons, and ingest_recommendation.

The ingest_recommendation field indicates if the project needs indexing for code search:

  • If [INGEST_RECOMMENDED] appears, ask the user if they want to enable semantic code search

  • Benefits: AI-powered code understanding, dependency analysis, better context retrieval

  • If user agrees, run: project(action="ingest_local", path="")

IMPORTANT: Pass the user's FIRST MESSAGE as context_hint to get semantically relevant context! Example: init(folder_path="/path/to/project", context_hint="how do I implement auth?")

This does semantic search on the first message. You only need context on subsequent messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auto_indexNoAutomatically create and index project from IDE workspace (default: true)
project_idNoProject to initialize context for (UUID, or a project name to look up)
session_idNoCustom session ID (auto-generated if not provided)
folder_pathNoCurrent workspace/project folder path (absolute). Use this when IDE roots are not available.
context_hintNoRECOMMENDED: Pass the user's first message here for semantic search. This finds relevant context from ANY time, not just recent items.
workspace_idNoWorkspace to initialize context for
is_post_compactNoSet true immediately after context compaction to restore snapshots/transcripts when hooks are unavailable. Can also be enabled by CONTEXTSTREAM_RESTORE_CONTEXT=true.
include_decisionsNoInclude recent decisions (default: true)
allow_no_workspaceNoIf true, allow session_init to return connected even if no workspace is resolved (workspace-level tools may not work).
include_recent_memoryNoInclude recent memory events (default: true)
skip_project_creationNoIf true, skip automatic project creation/matching. Use for parent folders containing multiple projects where you want workspace-level context but no project-specific context.
Behavior5/5

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

Describes the tool's behavior: initiates a session, retrieves context, suggests code ingestion. Annotations (readOnlyHint=false) do not contradict; description adds details about semantic search and output fields beyond annotations.

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?

Description is well-structured with clear sections, but slightly verbose. Could trim redundant details about ingest_recommendation benefits. Good use of examples and emphasis on important points.

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 11 parameters and no output schema, the description covers the main workflow, output contents, and edge cases like context compaction. Lacks information about authentication or error conditions, but overall comprehensive.

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 parameters are well-documented. Description adds value by explaining context_hint in depth with an example, and clarifies is_post_compact and skip_project_creation usage. Slightly redundant but helpful.

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 'Initialize a new conversation session' and specifies it's the first tool to call. The verb 'initialize' and resource 'conversation session' are specific and distinguishable from siblings like 'session'.

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 'This is the FIRST tool AI assistants should call when starting a conversation.' Provides guidance on using context_hint with the first message and handling ingest_recommendation. Also notes that subsequent messages don't need context.

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