No user-submitted related servers found.
Scored across 72 tools
Most tools partition cleanly by asset class and data type, but several overlapping pairs create ambiguity: get_corporate_actions vs. get_corporate_action_announcements, get_option_contracts vs. get_option_chain, and historical get_stock_quotes/get_crypto_quotes vs. the get_*_latest_quote tools. The descriptions clarify intent, but the tool names alone would often make selection error-prone.
The set predominantly follows a get_<resource> pattern with clear action prefixes like place_, cancel_, update_, delete_, and create_, making the convention easy to learn. Deviations include get_corporate_actions versus get_corporate_action_announcement(s) and historical quote tools that omit "historical" in their names, but there is no style mixing such as camelCase.
With 72 tools, this server far exceeds both the 25+ "too many" threshold and the 50+ "extreme mismatch" threshold. The Alpaca domain is broad and most tools are distinct, but exposing this many tools in one MCP server makes tool selection expensive and overwhelming for an agent.
The tool surface is highly comprehensive, covering account, orders, positions, watchlists, assets, market data for stocks/crypto/options/fixed income, news, calendar, corporate actions, locates, and API documentation. Order lifecycle and watchlist CRUD are complete, and there are no obvious dead ends in core workflows.