Skip to content

HTTP error messages lack response body details #1

@gabdorf

Description

@gabdorf

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions