Skip to content

fix: use suffix matching for MCP tool names in assertions#21

Merged
sonesuke merged 2 commits intomainfrom
fix/mcp-tool-name-matching
Mar 30, 2026
Merged

fix: use suffix matching for MCP tool names in assertions#21
sonesuke merged 2 commits intomainfrom
fix/mcp-tool-name-matching

Conversation

@sonesuke
Copy link
Copy Markdown
Owner

Summary

  • Change check_tool_use and check_param to match tool names using ends_with instead of exact equality
  • MCP tools have fully qualified names (e.g. mcp__plugin_google-patent-cli_google-patent-cli__search_patents), so exact match always failed
  • Aligns all 4 comparison sites with check_mcp_success which already used ends_with

Test plan

  • Verified with mise run skill-test on google-patent-cli: all 11 tests pass (was failing before)
  • cargo test passes

🤖 Generated with Claude Code

sonesuke and others added 2 commits March 30, 2026 04:43
`check_db_query` used `row.get::<_, String>(0)` which fails for
INTEGER columns like COUNT(*). Use `rusqlite::types::Value` to
handle Integer, Real, Text, Blob, and Null variants.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
MCP tools use fully qualified names (e.g. mcp__plugin_...__search_patents)
but check_tool_use and check_param used exact equality. This caused all
tool-use and tool-param assertions to fail for MCP tools. Change all 4
comparisons from == to ends_with, consistent with check_mcp_success.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@sonesuke sonesuke merged commit 4478155 into main Mar 30, 2026
4 checks passed
@sonesuke sonesuke deleted the fix/mcp-tool-name-matching branch March 30, 2026 10:48
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