stargate-mcp

The tools are distinct in their specific contract function calls, but there is significant overlap in purpose and naming that could cause confusion. For example, multiple redeem-related tools (redeemLocal, redeemLocalCallback, redeemLocalCheckOnRemote, revertRedeemLocal) have unclear boundaries, and tools like cachedSwapLookup and revertLookup are similarly vague. Descriptions help differentiate, but the high count and technical nature increase misselection risk.

Tool names follow a consistent camelCase pattern throughout, with clear verb-action naming (e.g., addLiquidity, createPool, setFees). Minor deviations include some tools with 'Lookup' suffixes and event names in PascalCase, but the overall convention is predictable and readable.

With 42 tools, the count is excessive for an MCP server, making it overwhelming and difficult to navigate. While the domain (Stargate contract interactions) is complex, this many tools suggests poor scoping, likely mapping directly to contract functions without aggregation, which hinders usability.

The tool set appears complete for interacting with the Stargate contract, covering core operations like liquidity management (addLiquidity, swap), pool configuration (createPool, setFees), cross-chain functions (redeemRemote, sendCredits), and ownership controls (transferOwnership, renounceOwnership). No obvious gaps are evident given the inferred domain.