A Model Context Protocol server that provides code symbol search and analysis capabilities across multiple programming languages via LSP (Language Server Protocol) adapters
Asteria provides three code-analysis tools with complete input schemas and basic descriptions. All tools have verb-noun naming (get_, find_) and documented parameters with types. However, descriptions are minimal (10-30 chars), lacking context on WHEN to use each tool, what they return, or how they differ. No output schemas are documented. Error handling is absent, no guidance on recovery or invalid input. Parameters lack constraints (enums, ranges, format hints). The tools are read-only and well-scoped, but descriptions fall short of the 50-200 char LLM-optimized baseline (baseline avg 194 chars). This is a typical community server: functional but underspecified for agent reasoning.
Find all symbols that reference a given symbol
Find symbols matching a query pattern with optional filtering by kind and scope
Get an overview of symbols in a file or workspace, grouped by symbol kind
Descriptions are too brief (10-30 chars) and lack context. 'Get an overview of symbols in a file or workspace, grouped by symbol kind' does not explain WHEN to call this vs find_symbol, what the output structure is, or what 'symbol kind' means to an LLM.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., symbol IDs, file paths, line numbers) without knowing the response structure.
Parameters lack constraints and format hints. 'depth' is an integer with no min/max (unbounded). 'include_kinds' and 'exclude_kinds' are arrays with no enum of valid symbol kinds. LLMs cannot validate inputs or know what values are acceptable.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | <=2025-11-25 | v2 |
No error handling or recovery guidance. If a workspace_root is invalid, a symbol is not found, or a query is malformed, the tool provides no actionable error message or next steps for the LLM.
Parameter descriptions are generic or missing context. 'The symbol name or pattern to search for' does not clarify whether regex, glob, or substring matching is supported, or what happens if no matches are found.