Skip to main content
Glama
contextstream

ContextStream MCP Server

Manage reusable skills

skill
Read-onlyIdempotent

Create, manage, and run reusable skill bundles (instructions + actions) across projects. List, import, export, and share skills to automate workflows.

Instructions

Manage and execute reusable skills (instruction + action bundles). Skills are portable across projects, sessions, and tools. Use 'supersede' to retire a stale skill (archives it so it stops surfacing).

Actions:

  • list: Browse skills (filter by scope, status, category)

  • get: Get skill details by ID or name

  • create: Define a new skill with name, instruction, and triggers

  • update: Modify an existing skill

  • run: Execute a skill (by ID or name)

  • delete: Remove a skill

  • import: Import skills from file or content (supports markdown, JSON, cursorrules, claude_md)

  • export: Export skills in various formats

  • share: Change skill visibility scope

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSkill name (slug, e.g. 'deploy-checker')
limitNoMax results to return
queryNoSearch query
scopeNoVisibility scope
titleNoSkill display title
actionYesThe action to perform
formatNoImport/export format
paramsNoParameters passed to skill execution
statusNoSkill status
actionsNoAction steps array [{type, tool, params, ...}]
contentNoContent string for import
dry_runNoPreview execution without running
categoryNoFilter by category tag
priorityNoSkill priority 0-100 (higher = matched first)
skill_idNoSkill ID (UUID)
file_pathNoLocal file path for import
skill_idsNoSkill IDs for export
categoriesNoTags for discovery/filtering
project_idNoProject ID (UUID)
descriptionNoSkill description
is_personalNoWhether skill is personal
source_fileNoSource filename (for import provenance)
source_toolNoSource tool name (for import provenance)
workspace_idNoWorkspace ID (UUID)
superseded_byNoReplacement skill (name or id), recorded when action='supersede'
trigger_regexNoOptional regex for advanced trigger matching
change_summaryNoSummary of changes (for version history)
instruction_bodyNoMarkdown instruction text (the prompt)
trigger_patternsNoKeywords/phrases for auto-activation
Behavior1/5

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

The annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description includes write actions (create, update, delete, import). This is a direct contradiction, causing confusion about the tool's behavior.

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?

The description is well-structured with a brief intro and bullet-pointed actions. It is of appropriate length and front-loads key information, though it could be slightly more concise.

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

Completeness3/5

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

Given the complexity (29 parameters, multiple actions), the description covers the tool's capabilities adequately. However, the annotation contradiction undermines completeness, and lack of output schema information is acceptable. Score penalized due to contradiction.

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 baseline is 3. The description adds some context for actions (e.g., supersede archives skills), but does not provide additional meaning for individual parameters beyond what's in 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 the tool manages and executes reusable skills, and lists all specific actions (list, get, create, update, run, etc.). It distinguishes from sibling tools by specifying its focus on skills.

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?

The description mentions skills are portable and gives a specific note about 'supersede' to retire stale skills. However, it does not explicitly state when to use this tool versus alternatives, but the purpose is clear enough.

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