Out of Context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUT_OF_CONTEXT_STORAGE_PATH | No | Path to the storage directory for contexts. | out_of_context |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delete_contextA | Delete context by name (forced eviction by agent). Supports both single and bulk operations. Single: provide 'name' (str). Bulk: provide 'names' (list[str]) or 'name' as list[str]. For bulk operations, returns list of results with errors for missing contexts. |
| get_contextA | Get context by name. Supports both single and bulk operations. Single: provide 'name' (str). Bulk: provide 'names' (list[str]) or 'name' as list[str]. Returns context with 'text' (markdown body) and 'metadata' (from frontmatter). For bulk operations, returns list of results with errors for missing contexts. |
| put_contextA | Add or update context by name. Supports both single and bulk operations. Single: provide 'name' (str), 'text' (str, markdown content), and optional 'metadata' (dict). Bulk: provide 'contexts' (list[dict]) where each dict has 'name', 'text', optional 'metadata'. Names must be filename-safe (alphanumeric, hyphens, underscores). Overwrites existing contexts with a warning. Contexts are stored as .mdc files (markdown with YAML frontmatter). |
| list_contextA | List all contexts, sorted by creation date (newest first). Returns list of contexts with 'name', 'created_at', and 'preview' (first 100 chars). Optional 'limit' parameter to limit number of results. |
| search_contextA | Search contexts by query string. Searches in both YAML frontmatter (metadata) and markdown body (text content). Returns matching contexts with 'name', 'text', 'metadata', and 'matches' (where query was found). Optional 'limit' parameter to limit number of results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_context_prompt | Create a new context with the specified name and content. This prompt template helps create a new context entry. The name must be filename-safe (alphanumeric, hyphens, underscores). The text should be markdown content, and optional metadata can be provided as a dictionary. |
| update_context_prompt | Update an existing context with new content. This prompt template helps update an existing context. If the context doesn't exist, it will be created. The text should be markdown content, and optional metadata can be provided to update the context's metadata. |
| get_context_prompt | Retrieve a context by name. This prompt template helps retrieve a specific context by its name. The context will be returned with its text content and metadata. |
| search_context_prompt | Search for contexts matching a query string. This prompt template helps search for contexts that match a query. The search looks in both metadata (YAML frontmatter) and text content. You can optionally limit the number of results. |
| list_contexts_prompt | List all available contexts. This prompt template helps list all contexts, sorted by creation date (newest first). You can optionally limit the number of results. |
| delete_context_prompt | Delete a context by name. This prompt template helps delete a specific context. This operation permanently removes the context and cannot be undone. |
| bulk_create_contexts_prompt | Create multiple contexts at once. This prompt template helps create multiple contexts in a single operation. Each context in the list should have 'name' and 'text' fields, and optionally a 'metadata' field. |
| bulk_get_contexts_prompt | Retrieve multiple contexts by name. This prompt template helps retrieve multiple contexts in a single operation. Returns results for all requested contexts, with errors for any that are not found. |
| bulk_delete_contexts_prompt | Delete multiple contexts by name. This prompt template helps delete multiple contexts in a single operation. This operation permanently removes the contexts and cannot be undone. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose (delete, get, list, put, search) with no overlap, making it easy for an agent to select the correct one.
All tools follow a consistent 'verb_context' pattern in snake_case, ensuring predictable and readable naming.
With 5 tools, the set is well-scoped for managing contexts, covering CRUD and search without unnecessary bloat.
The tool surface is complete for the domain: create/update (put), read (get/list), delete, and search—no obvious gaps.