Skip to content

fix: discover MCP SQL tools by capability - #596

Open
yashsahare05 wants to merge 1 commit into
supabase:mainfrom
yashsahare05:fix/mcp-sql-tool-discovery
Open

yashsahare05 wants to merge 1 commit into
supabase:mainfrom
yashsahare05:fix/mcp-sql-tool-discovery

Conversation

@yashsahare05

Copy link
Copy Markdown

Summary

Updates the Supabase skill so agents do not assume the MCP SQL execution
tool is exposed exactly as execute_sql.

The updated guidance:

  • discovers SQL tools by capability, description, and input schema
  • accepts namespaced or transformed tool names
  • invokes the exact tool name returned by the current registry
  • only falls back to MCP connection troubleshooting when no compatible
    SQL execution tool can be discovered
  • updates other execute_sql references to avoid requiring the exact name

Fixes #189

Testing

  • pnpm test

@yashsahare05

Copy link
Copy Markdown
Author

Hi maintainers,
The Skills CI workflow appears to have expired after waiting for approval for 30 days. No CI jobs were executed.
Could someone please review the PR and approve a fresh workflow run? I'm happy to address any feedback or make additional changes if needed.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

user-feedback: discover MCP SQL tools by capability instead of exact tool name

1 participant