fix: register gateway MCP tools for agents#72
Open
aaurix wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR registers the missing Gateway MCP tools that Condor agents already reference and that the official Condor MCP Tools documentation lists under Gateway (DEX Trading):
manage_gateway_container()for Gateway Docker lifecycle operationsmanage_gateway_config()for Gateway chains, networks, tokens, connectors, pools, and walletsmanage_gateway_swaps()for DEX swap quote, execution, search, and status operationsmanage_gateway_clmm()for CLMM liquidity position managementProblem
Condor's agent-facing documentation and internal agent safety logic expect Gateway MCP tools to be available, but the Hummingbot MCP server did not expose the complete Gateway tool surface.
Specifically:
manage_gateway_swaps(),manage_gateway_clmm(), andmanage_gateway_container()in the Gateway tool group.CONDOR.md, agent confirmation logic, and risk checks referencemanage_gateway_clmmfor LP position actions.The result is that agents can be instructed to use Gateway tools that are not registered in the MCP server, and Gateway container/config calls can fail at formatting time even after the API call succeeds.
Solution
This PR:
GatewayCLMMManageRequestfor CLMM position operations.manage_gateway_clmm()using the existinghummingbot-api-clientGateway CLMM router methods:open_positionclose_positioncollect_feesget_positions_ownedsearch_positionsmanage_gateway_clmm()inmcp_servers/hummingbot_api/server.py.manage_gateway_clmmto the agent MCP preload hint.Testing
Ran locally:
Results:
uv run pytest: 4 passedpy_compile: passedgit diff --check: passedNotes
The branch is based on the latest
origin/mainat commit2105d27and is focused on MCP Gateway tool registration and contract fixes.