Proposal: Tool active state #93
Description
I have a generic framework which allows developing desktop-style web apps. The framework has support for commands (similar to VS Code extension commands). These commands are already exposed as tools to LLMs. Each command can have one or more handler; at any time one handler should be active for the command to be executable.
What I propose is to allow tools registered into the WebMCP registry to also respect this dynamic aspect of when a tool can be executed.
This allows the LLMs to better plan when tools in more complex flows will be available after specific steps. When a tool is not enabled, the LLM "knows" it is generally available but not in the current app's state.