rarefaction
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATH | No | Set (e.g. via the client's --env) to include the directories of language servers such as rust-analyzer or wat_server that live outside the client's PATH, e.g. $HOME/.local/bin:$HOME/.cargo/bin:$PATH. | |
| CLAUDE_PROJECT_DIR | No | Claude Code's project directory, used as a fallback to determine the workspace root. An explicit --root takes precedence over CLAUDE_PROJECT_DIR, then the working directory. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orientA | Compact source context from language-server indexes: signature, body, callers, callees, tests, implementations and relevant files. Use before broad file reads in Swift, Rust, C/C++, TypeScript/JavaScript, Python and WebAssembly WAT projects. In mixed workspaces specify profile or use path:line:column. No cross-language/FFI edges are inferred. Increase up/down only when needed. |
| statusA | Check detected source-language profiles, project roots, executables, compile flags and freshness. Call once before orient in a new project or when orientation is incomplete. Pass profile/project to inspect a nested package. |
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 2 tools
orient performs the actual context retrieval while status is a diagnostic/setup check for profiles and freshness. The two purposes are clearly distinct with no overlap, and the descriptions explicitly state the call order (status before orient).
Both names are single lowercase tokens in a consistent style, but one is a verb (orient) and the other a noun (status), so there is no single predictable verb_noun convention. Still readable and non-chaotic.
Only two tools for a code-orientation/LSP-indexing domain feels thin; the surface is tightly scoped but leaves little room for related operations. It borders on under-provisioned for the apparent scope.
The pair covers orientation and environment checking, which are the core workflow, but there is no way to refresh/rebuild indexes, enumerate indexed projects, or query symbols separately. Notable gaps exist that an agent may hit in larger workflows.