squiggles
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| goto_definitionB | Go to the definition of a symbol at the given position. Returns the file and location where the symbol is defined. |
| goto_type_definitionA | Go to the type definition of a symbol. Returns where the type of the symbol at the given position is defined. |
| goto_implementationA | Go to implementations of an interface or abstract method. Returns concrete implementation locations. |
| goto_declarationB | Go to the declaration of a symbol (relevant in C/C++ for header declarations). |
| find_referencesA | Find all references to a symbol across the project. Returns every location where the symbol is used. |
| hoverA | Get hover information (type signature, documentation) for a symbol at the given position. |
| signature_helpB | Get parameter information for a function call at the given position. |
| document_symbolsB | Get all symbols (functions, classes, variables, etc.) defined in a file as a hierarchical tree. |
| workspace_symbolsA | Search for symbols across the entire project by name. Supports fuzzy matching. |
| code_actionsB | Get available code actions (quick fixes, refactorings) at the given position. Diagnostics overlapping the range are passed to the server so quick fixes are included. |
| formatA | Format a file using the language server's formatter and write the result to disk. |
| rename_prepareA | Check if a symbol at the given position can be renamed, and get its current name. |
| renameA | Rename a symbol across all affected files. Returns the workspace edit, or applies it to disk when apply is true. |
| call_hierarchy_incomingA | Find all functions/methods that call the function at the given position. |
| call_hierarchy_outgoingB | Find all functions/methods that are called by the function at the given position. |
| type_hierarchyB | Get the type hierarchy (supertypes and subtypes) for the type at the given position. |
| open_fileA | Open a file in the LSP server. This triggers diagnostics and makes the file available for subsequent no-arg diagnostics calls. |
| diagnosticsA | Get current diagnostics (errors, warnings) for a file. If no file is specified, returns diagnostics for all currently open files with issues. Waits for fresh results after recent edits. |
| ts_go_to_source_definitionA | Go to the source definition (the implementation, not the .d.ts declaration) of a symbol |
| ts_organize_importsA | Sort imports and remove unused ones in a TypeScript/JavaScript file. Applies the changes to disk. |
| ts_rename_fileA | Update all imports that reference a file after it has been moved or renamed on disk. Move the file first, then call this. Applies the changes to disk. |
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 21 tools
Each tool maps to a distinct LSP action (goto, references, rename, formatting, diagnostics, etc.). The several goto variants are clearly differentiated by description, and rename_prepare/rename, call_hierarchy_incoming/outgoing, and type_hierarchy are unambiguous.
The tools follow a consistent verb_noun snake_case pattern (goto_definition, find_references, rename_prepare, format). Minor deviations exist: 'goto' vs 'go_to' in ts_go_to_source_definition, and the ts_ prefix on TypeScript-specific tools, but these do not break the overall predictability.
At 21 tools, this is on the heavier side, but the server's purpose is to expose a comprehensive LSP surface, so the count is reasonable. Each tool covers a distinct LSP feature and none feel redundant, though the set could be trimmed by merging some goto variants.
The set covers core LSP workflows: navigation, references, rename, formatting, code actions, symbols, diagnostics, and call/type hierarchies. Minor gaps exist (e.g., no completion, document_highlight, or execute_command), but agents can accomplish most tasks without them.