Amazon Q MCP Client sends unsupported 'explanation' parameter to MCP Server

## Problem
Amazon Q MCP Client adds an 'explanation' parameter when calling MCP tools, which causes FastMCP servers with strict parameter validation to reject requests with 'unexpected_keyword_argument' errors.
https://github.com/sooperset/mcp-atlassian/issues/480


## Steps to Reproduce
- **MCP Client**: Amazon Q plugin for IDE
- **MCP Transport/Bridge**: npm remote-mcp
- **MCP Server**: SSE exposed Jira endpoints

https://github.com/geelen/mcp-remote
https://github.com/sooperset/mcp-atlassian

## Expected Behavior
Amazon Q should respect MCP tool schemas and only send defined parameters, or provide a configuration option to disable automatic parameter injection.

## Current Workaround
Explicitly instruct Amazon Q in prompt not to use explanation: "Connect to Jira and get issue with Id PRO-1234 but do not use explanation."

## System Details
- **OS**: Windows_NT x64 10.0.22631
- **Visual Studio Code**: 1.100.0
- **Amazon Q version**: 1.77.0
- **MCP Transport**: npm remote-mcp

Reproduce with Amazon Q 1.77.0 in VS Code 1.100.0 using the npm remote-mcp bridge and an SSE Jira endpoint; confirm that the strict FastMCP server rejects the injected explanation parameter. Trace the MCP tool-call handling and verify completion when only schema-defined parameters are sent, or when parameter injection can be disabled.

Written by the indexing model from the issue text.