forked from HAL9000/cleveragents-core
8ea00f5185
Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>
15 lines
849 B
Gherkin
15 lines
849 B
Gherkin
# @tdd_issue @tdd_issue_2158 @tdd_expected_fail @tdd_issue_4178 @skip
|
|
@skip
|
|
Feature: TDD Issue #2158 — MCPToolAdapter.invoke() error extraction uses non-standard key
|
|
MCPToolAdapter.invoke() currently reads error messages from result.get('error', 'unknown error'),
|
|
but the MCP 1.4.0 protocol returns errors in content[0].text. This means every error from a
|
|
real MCP 1.4.0 server is silently replaced with "unknown error".
|
|
|
|
# @tdd_issue @tdd_issue_4284 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: invoke() extracts error message from MCP 1.4.0 content array
|
|
Given a connected MCP adapter with a tool returning MCP 1.4.0 content-based error "read_file"
|
|
When I invoke "read_file" with arguments {"path": "/path/to/file"}
|
|
Then the invocation should fail
|
|
And the invocation error should contain "File not found: /path/to/file"
|