Add MCP client JSON encoding compatibility testing

[jonpspri]

MCP Client JSON Encoding Compatibility Testing

Problem Statement

Some MCP clients (e.g., Claude) still follow older protocol patterns of encoding complex objects/dictionaries in JSON before assigning them to nested attributes. The behavior of current DataBeak MCP servers when receiving this encoding format is unclear and needs validation.

Impact

Without proper testing and handling of legacy JSON encoding patterns:

• Clients using older MCP protocol implementations may experience failures
• Complex parameter passing could break silently
• DataBeak tools may not receive properly decoded parameters

Required Actions

1. Create test scripts using MCPClient or mcp-tool utilities that exercise legacy JSON encoding patterns
2. Identify compatibility gaps in current server implementation
3. Add handling code if servers don't properly decode JSON-encoded complex objects
4. Document supported encoding patterns for client integration

Technical Details

• Focus on tools that accept complex objects (nested dictionaries, arrays)
• Test parameter encoding/decoding in both directions
• Verify proper type validation with encoded parameters
• Ensure error handling works correctly with malformed encoded data

Acceptance Criteria

• Test scripts demonstrate current behavior with JSON-encoded parameters
• Any compatibility issues are identified and documented
• Server code handles both modern and legacy encoding patterns
• Integration tests validate compatibility with different client types

Priority

Medium - affects client compatibility but not core functionality