Skip to main content
Glama
contextstream

ContextStream MCP Server

Project

project
Read-onlyIdempotent

Oversee development work by listing, creating, updating, and deleting resources. Index and analyze files, merge sources, and track changes with git history.

Instructions

Project management. Actions: list, get, create, update, delete, index (trigger indexing), purge (completely de-index a project — removes file indices, code chunks, and search vectors but keeps the project record), forget_local (stop this machine from re-binding a folder to its saved scope; server data untouched), remove_paths (de-index specific files by exact path — pass paths=[...]), merge (merge source_project_id into project_id), overview, statistics, files, index_status, index_history (audit trail of indexed files), ingest_local (index local folder), team_projects (list all team projects - team plans only), recent_changes (git log/diff for recent file changes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the resource.
pageNoPage number for pagination.
pathNoLocal path to ingest
forceNoForce re-index all files, bypassing version check logic
limitNoMaximum commits to return (for recent_changes, default: 10, max: 50)
pathsNoExact indexed file paths (relative to the project root) to de-index (for remove_paths)
sinceNoFilter files indexed after this timestamp (ISO 8601)
untilNoFilter files indexed before this timestamp (ISO 8601)
actionYesAction to perform
branchNoFilter by git branch
sort_byNoSort field (default: indexed)
overwriteNoAllow overwriting existing files on disk.
page_sizeNoResults per page.
machine_idNoFilter by machine ID that indexed the files
project_idNoProject ID (UUID).
sort_orderNoSort order (default: desc)
descriptionNoShort description.
folder_pathNoAbsolute path to the local folder.
path_patternNoFilter by file path pattern (partial match)
workspace_idNoWorkspace ID (UUID).
write_to_diskNoWrite ingested files to disk before indexing.
source_project_idNoSource project ID to merge into project_id (for merge)
generate_editor_rulesNoInput parameter: generate editor rules.
Behavior1/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, but the description includes destructive actions like 'delete', 'purge', 'merge', and 'remove_paths' which modify or remove data. This is a clear contradiction. The description does add some detail for purge and forget_local, but fails to reconcile the overall destructive nature.

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

Conciseness2/5

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

The description is overly long and unstructured, consisting of a bullet list of 18 actions with only some inline explanations. It lacks clear front-loading of essential information. Could be organized into categories or brief descriptions for each action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (23 parameters, many actions, no output schema) and the contradictory annotations, the description fails to provide complete context. It doesn't explain row-level details like action dependencies, parameter relevance per action, or return values.

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 the schema provides parameter descriptions. The tool description does not add any extra semantic meaning beyond listing actions. No parameter usage context is given. Baseline 3 is appropriate.

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 description clearly states 'Project management' and enumerates 18 specific actions. It's obvious what the tool does, but it's a catch-all for many sub-operations, lacking a single focused verb+resource. However, it distinguishes itself from siblings by covering many project-related actions under one tool.

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

Usage Guidelines2/5

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

There are no guidelines on when to use this tool vs alternatives like workspace, entity, or vcs. For example, it doesn't explain when to use 'merge' vs 'update' or 'purge' vs 'delete'. No when-not-to-use or context is provided.

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