[DOCS] Missing LSP tool in primary reference and agent system instructions
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/settings#tools-available-to-claude
Section/Topic
The "Tools available to Claude" reference table in the public documentation and the corresponding tool definitions within the Agent System Prompt.
Current Documentation
The public table lists 17 tools (from AskUserQuestion to Write).
The internal system prompt (v2.1.12) used by the agent also lacks an entry for the LSP tool under its # Tools section, listing the same standard toolkit.
What's Wrong or Missing?
While the LSP Servers documentation and the v2.0.74 Changelog confirm the existence of an LSP tool for code intelligence (diagnostics, find-references, go-to-definition), the tool is entirely missing from:
- The primary public reference table: Making it difficult for users to know if the tool requires manual permission configuration.
- The Agent's internal system prompt: Even in version 2.1.12, the agent is not "explicitly" taught about an LSP tool in its core definitions, suggesting it is only treated as a dynamic capability provided via the plugin system.
This omission creates a "feature-gap" where users expect LSP capabilities (like real-time diagnostics sharing), but the primary documentation does not define the tool's parameters, timeouts, or permission requirements.
Suggested Improvement
Add a row to the "Tools available to Claude" table in settings.md:
| Tool | Description | Permission Required |
| :--- | :--- | :--- |
| LSP | Provides real-time code intelligence, including go-to-definition, find-references, and diagnostic sharing via Language Server Protocol. | No |
Additionally, ensure the internal agent definitions are updated so the model understands the LSP tool's scope alongside Read and Grep.
Impact
High - Prevents users from using a feature
Additional Context
- System Prompt Analysis: Analysis of the v2.1.12 (2026-01-17) hidden system prompt confirms that while tools like
Bash,Grep, andTodoWritehave explicit schemas provided to the model, the LSP tool is absent. - Inconsistency: The documentation encourages users to install LSP plugins (e.g.,
pyright-lsp,rust-lsp), yet the core tool used by those plugins is never defined in the master tool list. - Permission Clarity: Since diagnostics sharing happens automatically after edits (as per v2.0.74), defining this as a "No Permission Required" tool in the public docs will reduce user confusion regarding background activity.
3 Comments
What’s FIXED
While the primary request regarding the master tool table remains unaddressed, there have been significant updates to the surrounding documentation for LSP functionality:
.lsp.jsonconfiguration, including required fields (command,extensionToLanguage) and optional parameters likeinitializationOptionsandrestartOnCrash.What’s UNRESOLVED
The core issue reported in the original feedback remains unresolved:
Write). TheLSPtool is entirely absent from this list.LSPtool is not in the master list, there is no official confirmation in the settings documentation regarding its permission requirements. While the agent uses it for diagnostics and navigation, users cannot verify if it follows a "No Permission Required" model or if it can be restricted viadisallowedTools.LSPisn't defined as a primary tool, it is unclear if users can or should manage it withinTaskorAgentdefinitions.Conclusion
I am keeping this issue open.
Although the documentation for configuring LSP servers via the plugin system has improved, the LSP tool itself is still a "ghost" in the primary configuration and tools reference. For technical accuracy and parity with other internal tools like
GreporGlob, the LSP tool must be explicitly added to the table at https://code.claude.com/docs/en/settings#tools-available-to-claude. Users need a single source of truth to understand the scope and permission model of every tool the agent has at its disposal.Issue #19349 Verification
Title: [DOCS] Missing LSP tool in primary reference and agent system instructions
Issue Date: 2026-01-19
Verification Date: 2026-01-23
Status: RESOLVED
---
Issue Summary
I reported that the LSP tool was missing from the "Tools available to Claude" reference table at https://code.claude.com/docs/en/settings#tools-available-to-claude. The issue noted that while LSP Servers documentation existed in the plugins-reference page, the primary tools table did not include an entry for the LSP tool, making it difficult for users to understand its permission requirements and capabilities.
---
Verification Results
Claim 1: LSP tool missing from "Tools available to Claude" table
Status: RESOLVED
The LSP tool is now present in the tools table at line 869 of
settings.md:Verdict: Anthropic has added the LSP tool to the primary reference table with:
Claim 2: LSP Servers documentation exists but primary table was incomplete
Status: RESOLVED
The LSP Servers documentation still exists at
plugins-reference.md(lines 165-248), and the primary tools table now correctly references it. The documentation is consistent across both locations.Claim 3: Table listed 17 tools
Status: RESOLVED
The current table lists 21 tools:
---
Current State
| Claim | Status |
|-------|--------|
| LSP tool missing from tools table | RESOLVED |
| LSP documentation exists in plugins-reference | Still exists, now properly cross-referenced |
| Primary docs don't define tool parameters | RESOLVED - description now included |
---
Suggested Fix
N/A - Issue has been resolved.
---
References
---
Conclusion & Recommendation
Primary Concern: The LSP tool was not documented in the primary "Tools available to Claude" reference table.
Resolution Status: RESOLVED
Recommendation: CLOSE
Anthropic has added the LSP tool to the settings documentation with a comprehensive description that includes its capabilities (diagnostics, navigation operations), permission requirements (No), and a link to the code intelligence plugin documentation. The issue has been fully addressed.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.