Skip to main content
Glama
florpan
by florpan

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOLIDLSP_HOMENoOverride the directory where language servers are downloaded. Defaults to ~/.solidlsp.~/.solidlsp

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_infoA

Which repository this server bound to, and how. Answers cheaply without starting the language server — use it first to confirm the server is pointed at the project you think it is.

find_symbolA

Find a symbol by name anywhere in the project, resolved by the language server rather than by text search. Returns each match with its file and line.

document_symbolsA

Outline one file: every type, method, and field it declares, with line numbers. The API surface of the file without reading its body.

find_referencesA

Find everything that references a symbol — the real call/usage sites the compiler sees, including dependency-injection registrations and interface implementations that a text search misses. Run this before renaming, changing a signature, or deleting.

get_symbol_bodyA

The full source of one declaration, by name — a method, class or function — without reading the file it lives in. Use this instead of opening a file to look at a single member.

checkA

Compiler diagnostics for one file, from the already-running language server — errors and warnings in milliseconds, without a build. Run this after editing to confirm the change compiles.

find_definitionA

Jump to where a symbol is defined, resolved by the language server.

explain_symbolA

What a symbol is: resolved type, signature and documentation, plus its declaration line. Answers 'what does this call do' without opening the file.

blast_radiusA

What breaks if this symbol changes: everything that references it, then everything that references those, to the given depth. Run before changing a signature or deleting anything.

rename_symbolA

Rename a symbol everywhere, using the compiler's own understanding rather than text replacement — so it renames the right things and leaves unrelated same-named symbols alone. Defaults to a dry run showing what would change.

find_implementationsA

Find the concrete implementations of an interface or abstract member, or the overrides of a virtual one. Answers 'what actually runs when this is called', which references alone cannot tell you.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have distinct purposes, but a few overlap conceptually (e.g., find_symbol vs find_definition, explain_symbol vs get_symbol_body). The descriptions are detailed enough to reduce confusion, but an agent might still hesitate when selecting between similar navigation actions.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (find_symbol, find_references, rename_symbol, etc.), but a few deviate: project_info, check, and blast_radius are not verb-first. The naming is still readable and predictable overall, just with minor inconsistencies.

Tool Count5/5

With 11 tools, the server covers a comprehensive set of code navigation and analysis operations without being bloated. Each tool addresses a specific need, and the count fits well within the ideal range for a focused domain.

Completeness5/5

The tool set covers the full lifecycle of symbol exploration: finding, defining, referencing, implementing, renaming, inspecting, and checking diagnostics. It includes advanced features like blast radius and document outlines, leaving no obvious dead ends for common code navigation workflows.