Schema | chapel-support

chapel-support

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.

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanilaFe/chapel-support'

If you have feedback or need assistance with the MCP directory API, please join our Discord server