When the MCP tool get_calendar_events is called without the required accountId parameter, the current behavior appears to return an empty result set rather than a clear validation error.
This makes it difficult for clients and agents to detect that the request was malformed. Instead, the server should return a structured validation error indicating that the accountId parameter is required.
Suggested behavior:
- Validate required parameters before executing the request
- If accountId is missing, return a clear error response (for example a 400-style validation error or MCP error object)
- Include a message indicating that accountId is required for get_calendar_events
This would make the API easier for automated agents and tools to use reliably and would prevent silent failures where missing parameters produce empty results.
When the MCP tool get_calendar_events is called without the required accountId parameter, the current behavior appears to return an empty result set rather than a clear validation error.
This makes it difficult for clients and agents to detect that the request was malformed. Instead, the server should return a structured validation error indicating that the accountId parameter is required.
Suggested behavior:
This would make the API easier for automated agents and tools to use reliably and would prevent silent failures where missing parameters produce empty results.