Replaced hyphen with underscore in Sqlite & Sentry tools..

[rakesh-eltropy]

Description

Sqlite and Sentry MCP servers are not working of Amzaon Nova models as tool names do not accept hyphen in the name. It seems to be logical to me to have some sort of standard convention in the tool names. I checked all MCP Servers, all seems to follow tool names convention with this regular expression [a-zA-Z][a-zA-Z0-9_]* other than Sqlite and Sentry. I have replaced hyphen with underscore in these MCP servers.

Server Details

• Server: Sqlite, Sentry
• Changes to: tools

Motivation and Context

Sqlite and Sentry MCP servers are not working of Amzaon Nova models as tool names do not accept hyphen in the name. It seems to be logical to me to have some sort of standard convention in the tool names. I checked all MCP Servers, all seems to follow tool names convention with this regular expression [a-zA-Z][a-zA-Z0-9_]* other than Sqlite and Sentry. I have replaced hyphen with underscore in these MCP servers.

How Has This Been Tested?

I have tested the Sqlite MCP server with MCP client (https://github.com/rakesh-eltropy/mcp-client).

Breaking Changes

NA

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

NA

[jspahrsummers]

I think this is fine as a quick mitigation, but it's also probably reasonable to expect clients to perform sanitization as needed for the models they're using—MCP won't be able to track all restrictions imposed by different providers.

Thanks for the fix!