Name the Composio tools that actually exist - #126
Conversation
The system-prompt hint added in #36 tells every Composio-enabled bot to "run it with COMPOSIO_EXECUTE_TOOL". That tool does not exist. Queried the live endpoint the driver mounts (connect.composio.dev/mcp) with the repo's own key: tools/list returns seven tools, and calling COMPOSIO_EXECUTE_TOOL answers `-32602: Tool COMPOSIO_EXECUTE_TOOL not found`. The executor is COMPOSIO_MULTI_EXECUTE_TOOL, and the real flow has a middle step the hint skipped — a tool's arguments come from COMPOSIO_GET_TOOL_SCHEMAS. So the hint sent bots to a dead name on the one path it was written to unblock: a bot that trusts it burns its turn on a -32602 and then tells the user it has no access, which is exactly the outcome #36 set out to prevent. Now: SEARCH_TOOLS -> GET_TOOL_SCHEMAS -> MULTI_EXECUTE_TOOL. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 20 minutes Limit details: You’ve used all 3 included reviews currently available under your plan. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Comment |
The system-prompt hint from #36 tells every Composio-enabled bot to "run it with
COMPOSIO_EXECUTE_TOOL". That tool does not exist.I queried the live endpoint the driver actually mounts (
connect.composio.dev/mcp, using the repo's own configured key, through the same URL/header path asserver/composio.ts).tools/listreturns exactly seven tools:COMPOSIO_EXECUTE_TOOLis not among them and is not an alias — calling it returnsMCP error -32602: Tool COMPOSIO_EXECUTE_TOOL not found.Why it matters: a bot that trusts the hint burns its turn on a
-32602and then tells the user it has no access to the service — precisely the failure #36 was written to prevent. The hint also skipped a step: a tool's arguments come fromCOMPOSIO_GET_TOOL_SCHEMAS, so search → execute alone can't construct a valid call.The prompt now names the real flow:
COMPOSIO_SEARCH_TOOLS→COMPOSIO_GET_TOOL_SCHEMAS→COMPOSIO_MULTI_EXECUTE_TOOL.One line.
pnpm typecheckclean, 327 passed / 8 skipped.🤖 Generated with Claude Code