Skip to content

fix: mcpchecker task timeout, status mapping, and redaction prompt - #121

Merged
IlonaShishov merged 1 commit into
mcp-evaluation-pipelinefrom
fix/mcp-eval-bugs
Oct 26, 2026
Merged

IlonaShishov merged 1 commit into
mcp-evaluation-pipelinefrom
fix/mcp-eval-bugs

Conversation

@IlonaShishov

Copy link
Copy Markdown

Summary

  • eval.yaml: Use correct defaultTaskLimits.timeout field instead of defaultTaskTimeout which mcpchecker silently ignored — tasks ran with no timeout (edge-case-handling ran 23 minutes instead of 5)
  • aggregate_mcpchecker.py: Distinguish agent execution errors from judge failures in v1alpha2 output, so agent crashes map to "error" status ("not_evaluated" in the summary) instead of "failed"
  • sensitive-data-redaction.yaml: Rewrite prompt to be bounded like tool-correctness ("for each tool, invoke it once") instead of open-ended ("invoke several tools"), which caused incomplete agent responses with smaller models

Test plan

  • Verified behavioral-eval-summary.json is created in reports/ with correct three-state breakdown: pass=1 fail=1 not_evaluated=1
  • Confirmed task timeout field is recognized by mcpchecker per docs

🤖 Generated with Claude Code

- eval.yaml: use correct `defaultTaskLimits.timeout` field instead of
  `defaultTaskTimeout` which mcpchecker silently ignored, causing tasks
  to run with no timeout (edge-case-handling ran 23 minutes)
- aggregate_mcpchecker.py: distinguish agent execution errors from
  judge failures in v1alpha2 output so crashes map to "error" status
  (and "not_evaluated" in the summary) instead of "failed"
- sensitive-data-redaction.yaml: rewrite prompt to be bounded like
  tool-correctness ("for each tool, invoke it once") instead of
  open-ended ("invoke several tools"), which caused incomplete
  agent responses with smaller models

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@IlonaShishov
IlonaShishov merged commit a42cce8 into mcp-evaluation-pipeline Oct 26, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant