chapel-support
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHPL_HOME | No | The path to the Chapel installation directory. If not set, the server will try to auto-detect it. |
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 |
|---|---|
| list_primersB | Gets the list of available Chapel primers. |
| get_primerA | Gets a primer at the given path. The path must be an element of the list returned by list_primers. |
| compile_programD | – |
| list_chapel_lint_rulesA | Lists all available Chapel linting rules from chplcheck. Returns: A list of dictionaries, each containing: - 'name': The rule name - 'description': The rule description - 'is_default': Whether the rule is enabled by default |
| lint_chapel_codeA | Lints Chapel code using chplcheck and returns warnings and fixed code. Args: program_text: The Chapel code to lint program_name: The name of the program file fix: Whether to apply automatic fixes to the code custom_rules: List of specific rules to enable (if None, uses default rules) Returns: A dictionary containing linting results, which may include: - 'warnings': String containing linting warnings - 'fixed_code': The fixed code if fix=True - 'error': Error message if something went wrong - 'stats': Statistics about the linting process |
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 5 tools
Each tool targets a distinct operation: compilation, primer retrieval, linting, and listing rules or primers. Even though compile_program lacks a description, its name clearly distinguishes it from the others.
Tool names follow a consistent verb_noun pattern with underscores (e.g., compile_program, get_primer, list_primers). Minor inconsistency: lint_chapel_code and list_chapel_lint_rules include 'chapel' while others omit it, but overall pattern is clear.
With 5 tools, the server is well-scoped for a Chapel support utility. Each tool serves a clear purpose without redundancy or excess.
The tool set covers core Chapel operations: compilation, linting, and educational primers. A minor gap is the lack of a run or debug tool, but for a support-focused server the surface is adequate.