Summary

• Fixes Bug: Filter out None values in _run method of crewai_adapter.py #46 by implementing schema-aware filtering of None values in the CrewAI adapter
• Only filters None values when the parameter's schema doesn't explicitly allow null
• Preserves None values when schema allows them (e.g., type: ["string", "null"] or anyOf with null)

Problem

When using CrewAI with MCP servers like the GitHub MCP server, passing None values for optional parameters causes errors:

parameter head is not of type string, is <nil>

Solution

The fix inspects the tool's input schema before calling the MCP tool:

• If a parameter's schema allows null values, the None is preserved
• If the schema only allows non-null types (e.g., just "string"), the None value is filtered out
• This ensures compatibility with strict MCP servers while maintaining flexibility for servers that accept null

Test plan

• Added test case that reproduces the issue with a strict MCP server
• Test verifies None values are filtered when schema doesn't allow null
• All existing tests pass
• Linting and type checking pass