Skip to main content
Glama
bakshidwarak

Tavily Web Search MCP Server

by bakshidwarak

YOUR_TOOL_NAME

Search the web for information using natural language queries through the Tavily API.

Instructions

YOUR_TOOL_DESCRIPTION

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:28-30 (handler)
    The main handler function for the 'YOUR_TOOL_NAME' tool. It is decorated with @mcp.tool() which also handles registration. This is a placeholder implementation returning a static response.
    def YOUR_TOOL_NAME(query: str) -> str:
        """YOUR_TOOL_DESCRIPTION"""
        return "YOUR_TOOL_RESPONSE"
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. 'YOUR_TOOL_DESCRIPTION' gives no information about what the tool does, its effects (e.g., read/write, side effects), permissions, or limitations. It fails to compensate for the lack of annotations.

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

Conciseness2/5

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

The description is a single placeholder phrase 'YOUR_TOOL_DESCRIPTION', which is technically concise but represents under-specification rather than effective brevity. It lacks any structured information to guide the agent.

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

Completeness1/5

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

Given the tool has one parameter with 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It provides no context about functionality, parameters, or behavior, failing to meet even minimal requirements for a tool with this complexity.

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

Parameters1/5

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

Schema description coverage is 0%, with one required parameter 'query' undocumented in the schema. The description 'YOUR_TOOL_DESCRIPTION' adds no meaning about the parameter's purpose, format, or usage, leaving it completely unexplained.

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

Purpose1/5

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

The description 'YOUR_TOOL_DESCRIPTION' is a tautology that merely restates the tool name 'YOUR_TOOL_NAME' without specifying any actual functionality. It provides no verb, resource, or action, failing to distinguish from siblings like 'roll_dice' or 'web_search'.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. It lacks any context, prerequisites, or exclusions, leaving the agent with no information to decide between this tool and its siblings like 'roll_dice' or 'web_search'.

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