Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_diagnosticsA

Retrieve errors, warnings, and code hints for a file or the whole workspace. Use to check syntax/type errors after edits, before and after refactoring.

go_to_definitionB

Jump from a symbol position to its declaration/definition. Returns target file path, line, column, and optional surrounding code snippet.

find_referencesB

Find all references and usages of a symbol across the workspace. Returns file locations and compact line numbers. Use to assess impact of changes.

rename_symbolA

Rename a symbol across all workspace files via LSP. By default (apply=False), generates and returns a unified preview diff without modifying files. Requires apply=True AND writeChanges enabled in config to actually write changes to disk.

document_symbolsB

Retrieve outline of classes, methods, functions, and properties in a file. Use to quickly understand file architecture without reading all lines. Struct fields and enum members are collapsed into 'fields_count' by default unless include_fields=True.

workspace_symbolsB

Search for classes, methods, interfaces, and variables across the entire workspace. Much faster and more accurate than text search.

hoverA

Inspect type definitions, documentation strings, and signatures at a cursor position. Use to check parameter types, return values, and docstrings.

prepare_call_hierarchyC

Prepare a function or method for call hierarchy inspection. Verifies if the symbol supports call graphs.

call_hierarchyB

Trace caller/callee relationships for a function or method. direction='incoming' returns callers; direction='outgoing' returns called functions.

get_type_hierarchyB

Inspect class and interface inheritance hierarchy. direction='supertypes' returns base classes/interfaces; direction='subtypes' returns derived types.

lsp_statusA

Show status of all Language Server processes, active workspace root, process IDs, restart counts, and error summaries.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target clearly distinct LSP operations: diagnostics, status, definitions, references, rename, symbols, hover, and hierarchies. The only mild overlap is between prepare_call_hierarchy and call_hierarchy, where the preparatory step could be confused with the actual hierarchy query.

Naming Consistency4/5

Names are consistently snake_case and mostly follow verb_noun or clear noun_phrase patterns, e.g. go_to_definition, find_references, rename_symbol, get_type_hierarchy. Minor deviations include single-word hover and noun-style lsp_status/call_hierarchy, but the set remains predictable.

Tool Count5/5

Eleven tools is well-scoped for an LSP server, covering navigation, diagnostics, refactoring, symbols, and hierarchy queries without obvious bloat. Each tool appears to earn its place in the surface.

Completeness4/5

The server covers core LSP workflows: diagnostics, definition lookup, references, rename, document/workspace symbols, hover, and call/type hierarchies. Some secondary LSP capabilities such as code actions, formatting, or signature help are absent, but the main agent-facing operations are present.

Maintenance

ActivityMaintained
ResponsivenessNo issues