Skip to main content
Glama
vinitv

Tavily Web Search MCP Server

by vinitv
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

web_search

Search the web for information using natural language queries through the Tavily API. Get answers to questions by searching online sources.

Instructions

Search the web for information about the given query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:19-23 (handler)
    The handler function for the 'web_search' tool. It takes a query string, uses the TavilyClient to perform a web 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 full burden. It mentions 'Search the web' but doesn't disclose behavioral traits like rate limits, authentication needs, result format, pagination, or whether it's read-only or has side effects. The description is minimal and lacks essential operational context for an AI agent.

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 with no wasted words. It's appropriately sized for a simple tool and front-loaded with the core action. Every part of the sentence contributes to understanding the tool's basic function.

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 (web search can involve nuances like result types, sources, and limitations), no annotations, no output schema, and low parameter semantics, the description is incomplete. It doesn't address what the tool returns, how results are structured, or any operational constraints, making it inadequate for effective use by an AI agent.

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. It mentions 'query' as the parameter but doesn't elaborate on syntax, format, or examples. With schema description coverage at 0% and 1 parameter, the baseline is 4 for 0 parameters, but here it's 1 parameter with no schema descriptions, so the description partially compensates by implying the parameter's purpose but remains vague.

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') and resource ('the web') with a specific purpose ('for information about the given query'). It distinguishes itself from sibling tools like 'repair_cost' and 'roll_dice' by focusing on web information retrieval. However, it doesn't specify what type of web search (e.g., general, news, images) or differentiate from potential similar tools not present in this server.

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 prerequisites, limitations, or contexts where this tool is preferred over other methods. With sibling tools being unrelated ('repair_cost', 'roll_dice'), there's no explicit comparison or exclusion criteria provided.

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/vinitv/mcp-a11'

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