fix(gateway): make Slack platform note capability-aware when MCP tools present#6538
Open
ygd58 wants to merge 2 commits into
Open
fix(gateway): make Slack platform note capability-aware when MCP tools present#6538ygd58 wants to merge 2 commits into
ygd58 wants to merge 2 commits into
Conversation
…ty-aware platform notes
1 task
Collaborator
Collaborator
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes #6533
Problem
When Slack MCP tools are available at runtime, the gateway still injects a hardcoded platform note saying the agent has no Slack-specific API access. This causes false refusals even though Slack MCP tools are working.
Root Cause
build_session_context_prompt()had a hardcoded Slack platform note that always said Slack-specific APIs are unavailable, regardless of runtime tool availability.Fix
available_tools: List[str]field toSessionContextbuild_session_context()now acceptsavailable_toolsparameterbuild_session_context_prompt()checks for Slack tools (e.g.mcp_slack_*) inavailable_toolsrun.pypopulatesavailable_toolsfromget_all_tool_names()at message timeFiles Changed
gateway/session.py—SessionContext.available_toolsfield + capability-aware Slack note +build_session_context()signaturegateway/run.py— populateavailable_toolswhen building session context