Describe the bug
The problem: the git-issue-agent fails before any tool runs:
400 Invalid schema for function 'list_issue_types':
None is not of type 'object', 'boolean'
Steps To Reproduce
Use the agent with open ai
I only verified it with Token Broker - I need to verify it with token exchange or understand why (in case it only happened with token-broker)
Expected Behavior
Cause: crewai-tools converts MCP tool schemas into OpenAI function definitions and emits parameters: null for that tool. OpenAI 2.45.0 rejects null. The MCP server's own schema is valid — I read it at pkg/github/issues.go:543-551, a proper {type: "object", properties: {owner}, required: ["owner"]}.
Why now: a2a/git_issue_agent/pyproject.toml uses floors, not pins — crewai-tools[mcp]>=1.15.2, openai unpinned. Rebuilding resolved openai 2.45.0. Tellingly, that file's own comments discuss pinning around openai 2.24.0/2.30.0, so the resolved set has drifted well past what the code was written against.
Caveat: this is inferred from the error plus the version drift. I never captured the actual schema on the wire — my attempt to enable MCP command logging wrote to a file rather than stdout, and I reverted it. So "crewai-tools mangles it" is the strong hypothesis, not a proven fact. Worth confirming before pinning blindly.
Rossoctl Version
No response
Additional Context
No response
Describe the bug
The problem: the git-issue-agent fails before any tool runs:
400 Invalid schema for function 'list_issue_types':
None is not of type 'object', 'boolean'
Steps To Reproduce
Use the agent with open ai
I only verified it with Token Broker - I need to verify it with token exchange or understand why (in case it only happened with token-broker)
Expected Behavior
Cause: crewai-tools converts MCP tool schemas into OpenAI function definitions and emits parameters: null for that tool. OpenAI 2.45.0 rejects null. The MCP server's own schema is valid — I read it at pkg/github/issues.go:543-551, a proper {type: "object", properties: {owner}, required: ["owner"]}.
Why now: a2a/git_issue_agent/pyproject.toml uses floors, not pins — crewai-tools[mcp]>=1.15.2, openai unpinned. Rebuilding resolved openai 2.45.0. Tellingly, that file's own comments discuss pinning around openai 2.24.0/2.30.0, so the resolved set has drifted well past what the code was written against.
Caveat: this is inferred from the error plus the version drift. I never captured the actual schema on the wire — my attempt to enable MCP command logging wrote to a file rather than stdout, and I reverted it. So "crewai-tools mangles it" is the strong hypothesis, not a proven fact. Worth confirming before pinning blindly.
Rossoctl Version
No response
Additional Context
No response