fix(MCP): Added error status to traces in MCP server for tool calls

[fali007]

• I have added tests that cover my changes.
• If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
• PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
• (If applicable) I have updated the documentation accordingly.
  This PR aims to add trace status for failed error calls. This helps in grouping error calls by nature of failures.

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 393f1cc in 2 minutes and 8 seconds. Click for details.

• Reviewed 15 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. packages/opentelemetry-instrumentation-mcp/opentelemetry/instrumentation/mcp/instrumentation.py:253

• Draft comment:
  Consider checking not only the existence of the 'isError' attribute but also its truthiness (e.g. if hasattr(request.result, 'isError') and request.result.isError:) to avoid falsely flagging non-error cases. Also, review if including the full serialized result in the error status may expose sensitive data.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_ZsBwRrBV1xwdPFCP

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}