feet(tools+context): Dynamic tool reg #309
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gerboland
reviewed
Oct 6, 2025
|
Added a comment about supported protocols. |
|
My Cursor is still struggling with this, while it can enable the datasource toolset, it fails to recognise the tools as callable. I have verified the So I think Cursor is the problem for me. Should it update the list of tools in its MCP settings UI on the |
sd2k
reviewed
Oct 6, 2025
Comment on lines
+105
to
+110
| // ToolsetInfo provides information about a toolset | ||
| type ToolsetInfo struct { | ||
| Name string `json:"name" jsonschema:"required,description=The name of the toolset"` | ||
| Description string `json:"description" jsonschema:"description=Description of what the toolset provides"` | ||
| Enabled bool `json:"enabled" jsonschema:"description=Whether the toolset is currently enabled"` | ||
| } |
There was a problem hiding this comment.
Do you think it would be worth including ToolNames []string here, as a more concrete hint of what tools this contains?
Comment on lines
+285
to
+287
| - ✅ **stdio protocol** - Fully supported | ||
| - ❌ **SSE (Server-Sent Events)** - Not yet supported | ||
| - ❌ **Streamable HTTP** - Not yet supported |
There was a problem hiding this comment.
Huh, is this because notifications aren't as well supported over streamable HTTP?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dynamic Toolset Discovery and Loading
Summary
Adds dynamic toolset functionality that allows clients to discover and selectively enable tool categories at runtime, significantly reducing context window usage by only loading tools when needed.
Motivation
MCP tool descriptions can consume substantial context window space. By enabling dynamic discovery, clients only load the tools they actually need, preserving context for more important data.
Implementation
New flag:
--dynamic-toolsetsenables dynamic toolset modeDiscovery tools: Added grafana_list_toolsets and grafana_enable_toolset meta-tools
Notification support: Sends tools/list_changed notification when toolsets are enabled, triggering client refresh
Integration with --enabled-tools:
--enabled-tools=""--> no toolsets discoverable--enabled-tools="datasources,dashboards"--> only specified toolsets discoverableLimitations and client compatibility
Protocol Support:
✅ stdio protocol - Fully supported
❌ SSE (Server-Sent Events) - Not yet supported
❌ Streamable HTTP - Not yet supported
Client Support
✅ Supported: Cursor, VSCode (support notifications)
❌ Not yet: Claude Desktop, Claude Code (no notification support) there are open issues though for it
Known Behavior
Slight delay expected: There may be a few seconds of delay between calling grafana_enable_toolset and the tools becoming available in the client, as the client needs to receive and process the
tools/list_changednotification.Note: This is opt-in via the
--dynamic-toolsetsflag. Existing static tool registration remains the default behavior.How it works with Cursor.
Currently Sonnet 4.5 model selected - 1m tokens available for this conversation
Normal behavior all tools available:
At the beginning 13.9% of context used
How many tools are available 14.1%
List my prometheus datasources 14.8%
Dynamic tool discovery enabled with all tools discoverable.
At the beginning 5.5% of context used
List available toolsets - 5.9%
Enable Datasource toolset
List Datasources 7%
