Skip to main content
Glama
contextstream

ContextStream MCP Server

Project

project
Read-onlyIdempotent

List, create, update, delete, index files, and access overview, statistics, file history, team workspaces, and recent changes.

Instructions

Project management. Actions: list, get, create, update, delete, index (trigger indexing), 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
actionYesAction to perform
workspace_idNoWorkspace ID (UUID).
project_idNoProject ID (UUID).
nameNoName for the resource.
descriptionNoShort description.
folder_pathNoAbsolute path to the local folder.
generate_editor_rulesNoInput parameter: generate editor rules.
pathNoLocal path to ingest
overwriteNoAllow overwriting existing files on disk.
write_to_diskNoWrite ingested files to disk before indexing.
forceNoForce re-index all files, bypassing version check logic
machine_idNoFilter by machine ID that indexed the files
branchNoFilter by git branch
sinceNoFilter files indexed after this timestamp (ISO 8601)
untilNoFilter files indexed before this timestamp (ISO 8601)
path_patternNoFilter by file path pattern (partial match)
sort_byNoSort field (default: indexed)
sort_orderNoSort order (default: desc)
limitNoMaximum commits to return (for recent_changes, default: 10, max: 50)
pageNoPage number for pagination.
page_sizeNoResults per page.
Behavior1/5

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

Annotations declare readOnlyHint: true, but description includes mutating actions (create, update, delete, ingest_local). This is a direct contradiction. Also, no disclosure of side effects like file system writes for ingest_local.

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 a single comma-separated list of actions, which is somewhat concise but not well-structured. A clearer format (e.g., bullet points or sections) would improve readability.

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?

While the description covers many actions, it lacks information about return values, behavior, or examples. Given the complexity (21 parameters, 14 actions), the description is incomplete without an output schema or behavioral details.

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?

All 21 parameters have descriptions in the schema (100% coverage). The description only lists actions and does not add meaning beyond the schema, so baseline score of 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 states 'Project management' and enumerates specific actions (list, get, create, etc.), making clear it covers CRUD and project-related operations. This distinguishes it from sibling tools like workspace or search.

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?

No guidance on when to use this tool versus alternatives (e.g., workspace for workspace-level operations). The list of actions implies use cases but doesn't provide context or exclusions.

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