feat(api)!: add toolset prompts infrastructure #581
Conversation
docs/PROMPTS.md
Outdated
| ```toml | ||
| disable_toolset_prompts = true |
There was a problem hiding this comment.
@nader-ziada will this be a global option, or a per-toolset option?
There was a problem hiding this comment.
global option currently
There was a problem hiding this comment.
I believe I included this in #556
Disabling Toolset Prompts
Administrators can disable all toolset-defined prompts via configuration, using only config-defined prompts:
based on what Nader initially implemented in #510
IMO maybe we SHOULD NOT provide this option at all (prompts don't have any involuntary impact on the LLM behavior or consume context-window tokens)
OR if you consider this of value, provide a consistent implementation with what we have for tools (EnabledTools / DisabledTools).
There was a problem hiding this comment.
for the sake of simplicity, will remove the flag completely
Enable toolset implementers to define MCP prompts programmatically as part of their toolset definition. - Add GetPrompts() method to Toolset interface - Collect prompts from all enabled toolsets - Merge config and toolset prompts (config takes precedence) - Add disable_toolset_prompts configuration option - Update all existing toolsets to implement GetPrompts() Signed-off-by: Nader Ziada <[email protected]>
nader-ziada
force-pushed
the
2-toolset-prompts
branch
from
691a239 to
c8bb280
Compare
manusa
changed the title
manusa
changed the title
Signed-off-by: Nader Ziada <[email protected]>
3 participants
Fixes: #556
Enable toolset implementers to define MCP prompts programmatically as part of their toolset definition.