Summary
Targeting gopls@v0.21.0, we are adding telemetry to collect usage metrics for all tools provided by the gopls MCP server. These counters are necessary to understand mcp tool usage and inform future decisions regarding tool support.
gopls/mcp-tool:go_context - user requests context for a region within a Go file. gopls/mcp-tool:go_diagnostics - user requests Go workspace diagnostics. gopls/mcp-tool:go _file_context - user requests a summary of a file's cross-file dependencies. gopls/mcp-tool:go_file_diagnostics - user requests diagnostics for a Go file. gopls/mcp-tool:go_file_metadata - user requests metadata about the Go package containing a file. gopls/mcp-tool:go_package_api - user requests a summary of a Go package API. gopls/mcp-tool:go_references - user requests the locations of references to a given object. gopls/mcp-tool:go_search - user searches for symbols in the Go workspace. gopls/mcp-tool:go_symbol_references - user requests the locations of references to a package-level Go symbol. gopls/mcp-tool:go_workspace - user requests a summary of the Go workspace. gopls/mcp-tool:go_vulncheck - user runs a vulnerability check on the Go workspace.
Proposed Config Change
https://go-review.googlesource.com/c/telemetry/+/703256
Comment From: gopherbot
Change https://go.dev/cl/703256 mentions this issue: internal/chartconfig: update config to add MCP server tool usage
Comment From: gabyhelp
Related Issues
- x/telemetry/config: add counters for MCP server usage #74341 (closed)
- x/tools/gopls: add counters for MCP server usage #74291 (closed)
- x/tools/gopls: add instrumentation to gopls MCP server calls #75448 (closed)
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
Comment From: findleyr
This makes sense to me. Let's give it a couple more days before approving.