Title: Deep Research Agent tool name mismatch causes repeated search and skipped extract follow-up
Describe the bug
Deep Research example uses hyphenated tool names in code (tavily-search, tavily-extract), but MCP registers underscored names (tavily_search, tavily_extract).
This mismatch breaks name-based branch logic, so follow-up extraction is not triggered as expected, and the agent repeatedly calls tavily_search for already-covered information.
To Reproduce
Steps to reproduce the behavior:
Configure required API keys and run examples/agent/deep_research_agent/main.py.
Use a query that needs search + extract (for example: find specific value from a Wikipedia page and calculate based on it).
Check logs:
MCP tools are registered as tavily_search, tavily_extract, etc.
Agent repeatedly calls tavily_search with similar intent.
Extract follow-up is not consistently triggered.
Expected behavior
Tool names should be consistent across registration, prompt instructions, and runtime checks, so:
tavily_search and tavily_extract are correctly recognized,
follow-up extraction runs when needed,
redundant repeated searches are reduced.
Error messages
No crash/exception in this case.
Observed behavior is logical mismatch:
registered names use underscore,
internal checks use hyphen,
repeated search loops appear in runtime history.
Environment (please complete the following information):
AgentScope Version: [please fill from local]
Python Version: [please fill from local]
OS: Linux
Additional context
I can provide reproducible artifacts:
2 markdown files (prompt-related context)
1 runtime log markdown file showing tool registration and repeated tavily_search calls
Proposed fix
Unify Tavily tool names to underscore format in Deep Research example:
tavily-search -> tavily_search
tavily-extract -> tavily_extract
Update all related name-based checks and defaults to use the same underscore naming (including truncation logic and follow-up trigger conditions).
Friday260331165601_detailed_report.md
Friday260401105412_detailed_report.md
log_260331165538.md
log_260401105410.md
Title: Deep Research Agent tool name mismatch causes repeated search and skipped extract follow-up
Describe the bug
Deep Research example uses hyphenated tool names in code (tavily-search, tavily-extract), but MCP registers underscored names (tavily_search, tavily_extract).
This mismatch breaks name-based branch logic, so follow-up extraction is not triggered as expected, and the agent repeatedly calls tavily_search for already-covered information.
To Reproduce
Steps to reproduce the behavior:
Configure required API keys and run examples/agent/deep_research_agent/main.py.
Use a query that needs search + extract (for example: find specific value from a Wikipedia page and calculate based on it).
Check logs:
MCP tools are registered as tavily_search, tavily_extract, etc.
Agent repeatedly calls tavily_search with similar intent.
Extract follow-up is not consistently triggered.
Expected behavior
Tool names should be consistent across registration, prompt instructions, and runtime checks, so:
tavily_search and tavily_extract are correctly recognized,
follow-up extraction runs when needed,
redundant repeated searches are reduced.
Error messages
No crash/exception in this case.
Observed behavior is logical mismatch:
registered names use underscore,
internal checks use hyphen,
repeated search loops appear in runtime history.
Environment (please complete the following information):
AgentScope Version: [please fill from local]
Python Version: [please fill from local]
OS: Linux
Additional context
I can provide reproducible artifacts:
2 markdown files (prompt-related context)
1 runtime log markdown file showing tool registration and repeated tavily_search calls
Proposed fix
Unify Tavily tool names to underscore format in Deep Research example:
tavily-search -> tavily_search
tavily-extract -> tavily_extract
Update all related name-based checks and defaults to use the same underscore naming (including truncation logic and follow-up trigger conditions).
Friday260331165601_detailed_report.md
Friday260401105412_detailed_report.md
log_260331165538.md
log_260401105410.md