contxt-box
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Return MCP server process info, including fixed active root. |
| set_rootC | Switch the active ConTXT BOX root during this chat. |
| update_indexB | Update the lazy workspace index. |
| healthA | Run ConTXT BOX operational readiness checks. |
| searchC | Search indexed workspace metadata. |
| get_fileC | Return secure file metadata for a workspace path. |
| pull_contextC | Return a compact context bundle for a task. |
| extract_mediaC | Extract and permanently cache media context. |
| reorganizeC | Preview an intelligent reorganization plan. |
| auto_preserve_contextC | Persist high-level chat context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes (e.g., auto_preserve_context vs. extract_media, pull_context), but some overlap exists between context preservation tools, potentially causing confusion.
Naming is mixed: some tools follow verb_noun (get_file, set_root, update_index), while others are just verbs (health, reorganize) or use different styles (server_info). This inconsistency reduces predictability.
With 10 tools, the count is well within the ideal 3-15 range and appropriate for a context management server, covering essential operations without bloat.
The tool set covers core context operations like preservation, extraction, search, and reorganization. Missing explicit update/delete for context items, but overall it provides a coherent workflow for the domain.