fix: no wrappers

[scottschreckengaust]

Added warning about merging new MCP servers that are primarily wrappers around an AWS SDK.

Fixes

Summary

Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have reviewed the contributing guidelines
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Is this a breaking change? (Y/N)

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[scottschreckengaust]

Do we need to include more details of what a wrapper is in the contributing or developers guide?

[krokoko]

Yeah, I would expand on the definition (or provide some sort of checklist). For each tool exposed:

• can this action be achieved through the api mcp server ? If yes, then we don't take it
• Is it simply a wrapper around a boto3 call, a.k.a it does not add any logic or enhanced functionality ? If yes, we don't take it