Skip to main content
Glama
mwalker-tmd

Tavily Search MCP Server

by mwalker-tmd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

YOUR_TOOL_NAME

Search the web for current information using natural language queries to retrieve up-to-date data from the internet through the Tavily API.

Instructions

YOUR_TOOL_DESCRIPTION

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:27-30 (handler)
    The main handler function for the 'YOUR_TOOL_NAME' tool, decorated with @mcp.tool() for registration. It takes a query string and returns a placeholder response.
    @mcp.tool()
def YOUR_TOOL_NAME(query: str) -> str:
    """YOUR_TOOL_DESCRIPTION"""
    return "YOUR_TOOL_RESPONSE"
  • server.py:27-27 (registration)
    The @mcp.tool() decorator registers the YOUR_TOOL_NAME tool with the MCP server.
    @mcp.tool()
  • server.py:28-28 (schema)
    Type hints define the input schema (query: str) and output (str).
    def YOUR_TOOL_NAME(query: str) -> str:

Tool Definition Quality

D1.1/5.0
Behavior1/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, but 'YOUR_TOOL_DESCRIPTION' offers no information about the tool's behavior, such as whether it performs read/write operations, requires authentication, has side effects, or handles errors. It fails to describe any behavioral traits beyond the placeholder text.

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?

While the description is technically concise with a single word, it is under-specified rather than efficiently informative. The placeholder 'YOUR_TOOL_DESCRIPTION' does not earn its place as it provides no useful content, making it ineffective despite its brevity.

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 1 parameter with no schema descriptions, no annotations, no output schema, and sibling tools, the description is completely inadequate. It fails to address any contextual aspects, such as the tool's role among siblings or how it complements other tools, leaving the agent with insufficient information to use it correctly.

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?

The input schema has 1 required parameter with 0% description coverage, and the description 'YOUR_TOOL_DESCRIPTION' adds no meaning or context about the 'query' parameter. It does not explain what the query represents, its format, or how it influences the tool's operation, leaving the parameter undocumented.

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 providing any meaningful information about what the tool actually does. There is no verb, resource, or specific functionality mentioned, making it impossible to understand the tool's purpose.

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 provides no guidance on when to use this tool, when not to use it, or how it relates to sibling tools like 'roll_dice' and 'web_search'. There are no contextual cues, prerequisites, or alternatives mentioned, leaving the agent with no usage instructions.

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