Skip to main content
Glama
mwalker-tmd

Tavily Search MCP Server

by mwalker-tmd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

web_search

Search the web to find current information and answers using natural language queries, enabling AI models to retrieve up-to-date internet data.

Instructions

Search the web for information about the given query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:12-16 (handler)
    The web_search tool handler, decorated with @mcp.tool() for registration in FastMCP. It takes a query string, uses the global TavilyClient to 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
  • server.py:12-12 (registration)
    The @mcp.tool() decorator registers the web_search function as an MCP tool.
    @mcp.tool()
  • server.py:10-10 (helper)
    Initialization of the TavilyClient instance used by the web_search tool for performing web searches.
    client = TavilyClient(os.getenv("TAVILY_API_KEY"))

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Search the web' but doesn't specify aspects like rate limits, authentication needs, result format, or potential side effects (e.g., whether it accesses external APIs or has usage constraints). 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 unnecessary words. It's front-loaded with the core action ('Search the web'), making it easy to parse. Every part of the sentence contributes essential information, achieving optimal conciseness for such a straightforward tool.

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 moderate complexity (web search with external dependencies), no annotations, no output schema, and low schema coverage, the description is insufficiently complete. It lacks details on behavioral traits, result handling, error conditions, or usage constraints, which are critical for an AI agent to invoke this tool effectively in varied contexts.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It adds meaning by explaining that the 'query' parameter is used to search for information on the web, which clarifies its purpose beyond the schema's basic type definition. However, it doesn't provide details on query formatting, length limits, or examples, resulting in only partial compensation.

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 action ('Search the web') and the resource ('information about the given query'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'roll_dice' or 'YOUR_TOOL_NAME', but those are unrelated, so differentiation isn't critical here. The description avoids tautology by specifying what kind of search it performs.

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 or in what context it's appropriate. It simply states what it does without indicating any prerequisites, limitations, or scenarios where it might be preferred over other tools. This lack of usage context leaves the agent with minimal 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/mwalker-tmd/MCP-Session-Code'

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