Rell language intelligence over MCP. Provides language server protocol (LSP) capabilities for the Rell language used in Chromia blockchain projects.
11 tools with clear verb-noun naming (start_lsp, open_document, get_diagnostics). All have descriptions (avg 180 chars, within 10-1024 baseline). Input schemas present with typed parameters. However, output schemas are undocumented, tools return text/JSON without declared structure. Parameter descriptions are present but sparse (avg 40 chars vs 72 baseline). No enum constraints on parameters. Error handling is minimal, no recovery guidance or actionable error messages. Missing tool annotations (readOnlyHint, destructiveHint). Composition is sound: tools chain logically (open → get_diagnostics → close). No security issues detected (no secrets in params). Naming is consistent but could be more specific (e.g., 'get_info_on_location' is vague vs 'get_hover_info').
Close a file in the language server to free the resources it holds. Good practice for files no longer being analyzed, especially in long sessions or large codebases.
Get the code actions available for a range in a file: refactorings and quick fixes such as adding an import or fixing an error. Pass a result to apply_code_action to apply it. Requires the file to be opened first.
Get completion suggestions at a location in a file: names in scope, members, and callables valid at that point. Useful for discovering what a library or module offers. Requires the file to be opened first.
Get the definition location(s) of the symbol at a location in a file. Use it to jump to where a function, variable, entity, or type is declared. Requires the file to be opened first.
Get diagnostics (errors, warnings) for open files: syntax errors, type mismatches, and anything else the language server reports. Without a file path, returns diagnostics for every open file. Requires the files to be opened first.
Output schemas undocumented. Tools return text/JSON (e.g., lspToJson(completions)) without declaring structure. LLMs cannot plan downstream calls or extract fields reliably.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without parsing descriptions.
Error handling lacks recovery guidance. Errors like 'File not open' are stated but do not suggest next steps (e.g., 'Call open_document first').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Get hover information at a location in a file: type information, documentation, and other context about the symbol there. Use it to understand what a function or variable is in that context. Requires the file to be opened first.
Find every reference to the symbol at a location in a file, across the workspace. Requires the file to be opened first.
Open a file in the language server for analysis. Diagnostics, hover, and completions all require the file to be open. It stays open until explicitly closed.
Restart the language server process. Use this to reset the server when it becomes unresponsive or holds stale state, or to switch to a different project root.
Notify the language server that a file was saved, so it refreshes its diagnostics for the version currently on disk.
Start the Rell language server for a project. IMPORTANT: this must be called before any other LSP tool. The root directory should be the project's base folder — the one holding chromia.yml and the src/ directory. Defaults to the server's working directory, which is the directory mounted into the container.
Parameter descriptions are sparse (avg 40 chars vs 72 baseline). 'line' and 'column' lack format hints (0-indexed? 1-indexed?). 'include_declaration' boolean lacks default behavior explanation.
Tool name 'get_info_on_location' is vague. 'get_hover_info' or 'get_symbol_info' would be clearer. Ambiguous names cause LLM confusion when many tools exist.