Skip to main content
Glama
mcp2everything

MCP2Tavily

search_web_info

Search the web for information using the Tavily API to answer user queries in real-time.

Instructions

从网络搜索用户查询的信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • The handler function for the 'search_web_info' tool. It is decorated with @mcp.tool() for registration and delegates the search logic to the _do_search helper function.
    @mcp.tool()
    def search_web_info(query: str) -> str:
        """从网络搜索用户查询的信息"""
        return _do_search(query)
  • Supporting utility function that performs the actual web search using TavilyClient, processes the response including answer and top 3 sources, handles UTF-8 encoding issues, and formats the output.
    def _do_search(query: str) -> str:
        """Internal function to handle the search logic with UTF-8 support"""
        try:
            # 确保查询字符串是UTF-8编码
            query = query.encode('utf-8').decode('utf-8')
            tavily_client = TavilyClient(api_key=API_KEY)
            response = tavily_client.search(
                query=query,
                search_depth="basic",
                include_answer=True,
                include_raw_content=False
            )
            
            # 确保响应文本是UTF-8编码
            answer = response.get('answer', 'No answer found').encode('utf-8').decode('utf-8')
            sources = response.get('sources', [])
            
            result = f"Answer: {answer}\n\nSources:"
            for source in sources[:3]:
                title = source.get('title', 'No title').encode('utf-8').decode('utf-8')
                url = source.get('url', 'No URL')
                result += f"\n- {title}: {url}"
                
            return result
        except UnicodeError as e:
            logger.error(f"Encoding error: {str(e)}")
            return "Error: Unicode encoding issue occurred"
        except Exception as e:
            logger.error(f"Search error: {str(e)}")
            return f"Error performing search: {str(e)}"
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It mentions searching the web but doesn't describe how results are returned (e.g., format, pagination), potential rate limits, authentication needs, or whether it's read-only or has side effects. This leaves significant gaps for a tool interacting with external resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Chinese with no wasted words. It's appropriately sized and front-loaded, though brevity contributes to gaps in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavior, parameters, and output, making it inadequate for a tool that likely involves complex web interactions and sibling alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It implies a 'query' parameter but doesn't add meaning beyond the schema's basic type (string), such as examples, constraints, or how the query is processed (e.g., search engine used, language support).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '从网络搜索用户查询的信息' (search information from the web for user queries) states a clear purpose with a verb ('search') and resource ('information from the web'), but it's vague about what type of information it returns and doesn't distinguish from sibling tools like 'search_web' or 'get_url_content'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'search_web' or 'get_url_content'. The description implies a general web search but doesn't specify use cases, exclusions, or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcp2everything/mcp2tavily'

If you have feedback or need assistance with the MCP directory API, please join our Discord server