Problem
When HTTP errors occur in tool operations, the error messages don't include the response body from the API. This makes debugging difficult because users can't see what the API actually returned.
Current Behavior
Error messages look like:
HTTP error (client_error): Request failed with status 400
Expected Behavior
Error messages should include:
- The operation that failed
- The response body from the API
Example:
Failed to create task: HTTP error (client_error): Request failed with status 400 - Response: {"error": "Invalid field value"}
Location
src/tools/errors.ts - wrapToolError() function
Problem
When HTTP errors occur in tool operations, the error messages don't include the response body from the API. This makes debugging difficult because users can't see what the API actually returned.
Current Behavior
Error messages look like:
Expected Behavior
Error messages should include:
Example:
Location
src/tools/errors.ts-wrapToolError()function