llm-context
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lc_changedB | Returns list of files modified since given timestamp. Args: root_path: Root directory path (e.g. '/home/user/projects/myproject') timestamp: Unix timestamp to check modifications since |
| lc_outlinesC | Returns excerpted content highlighting important sections in all supported files. Args: root_path: Root directory path rule_name: Rule to use for file selection rules timestamp: Context generation timestamp to check against existing selections |
| lc_rule_instructionsC | Provides step-by-step instructions for creating custom rules. Args: root_path: Root directory path |
| lc_missingC | Unified tool for retrieving missing context (files, implementations, or excluded sections). Args: root_path: Root directory path (e.g. '/home/user/projects/myproject') param_type: Type of data - 'f' for files, 'i' for implementations, 'e' for excluded sections data: JSON string containing the data (file paths in /{project-name}/ format or implementation queries) timestamp: Context generation timestamp |
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 4 tools
The tools have distinct purposes: lc_changed identifies modified files, lc_missing retrieves missing context, lc_outlines highlights important sections, and lc_rule_instructions provides rule creation guidance. There is minor potential overlap between lc_missing and lc_outlines in handling file content, but their specific focuses (missing vs. highlighted sections) keep them mostly separate.
All tool names follow a consistent 'lc_' prefix with descriptive suffixes (changed, missing, outlines, rule_instructions). This uniform pattern makes the tools easily identifiable as part of the same set and aligns with the server's 'llm-context' theme.
With 4 tools, the count is reasonable for a context management server, covering key operations like tracking changes, retrieving missing data, outlining content, and rule creation. It might benefit from additional tools for advanced context manipulation, but the core functionality is well-represented.
The tools cover essential context management tasks: monitoring changes, filling gaps, summarizing content, and rule setup. However, there are notable gaps, such as tools for deleting or updating context rules, managing context history, or integrating with external systems, which could limit agent workflows in more complex scenarios.