Skip to main content
Glama
bakshidwarak

Tavily Web Search MCP Server

by bakshidwarak
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

web_search

Search the web for information using natural language queries to find answers and data from the internet.

Instructions

Search the web for information about the given query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:12-16 (handler)
    The handler function for the 'web_search' tool, decorated with @mcp.tool() for registration. It takes a query string, uses the global TavilyClient to perform the search, and returns the search results.
    @mcp.tool()
def web_search(query: str) -> str:
    """Search the web for information about the given query"""
    search_results = client.get_search_context(query=query)
    return search_results

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool searches the web but doesn't add context like rate limits, authentication needs, result format, or potential side effects (e.g., network calls). This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 that directly states the tool's function without any wasted words. It is appropriately sized and front-loaded, making it easy to understand quickly.

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 the tool's complexity (a web search with potential behavioral nuances), lack of annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It doesn't cover return values, error handling, or operational details, making it inadequate for full agent understanding.

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

Parameters3/5

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

The description adds minimal meaning beyond the input schema, which has 0% description coverage. It implies the 'query' parameter is used for searching, but doesn't elaborate on syntax, constraints, or examples. With one parameter and low schema coverage, the description provides some context but doesn't fully compensate for the lack of detailed parameter documentation.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Search') and resource ('the web'), and it specifies the action is for information about a query. However, it doesn't differentiate from siblings like 'roll_dice' or 'YOUR_TOOL_NAME', which have unrelated purposes, so it's not fully distinct in context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, exclusions, or prerequisites, such as when web search is appropriate compared to other tools or methods, leaving the agent with minimal usage direction.

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/bakshidwarak/AIE8-MCP-Session'

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