Tavily Web Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | Yes | Your Tavily API key for web search capabilities |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Search the web for information about the given query |
| roll_diceC | Roll the dice with the given notation |
| YOUR_TOOL_NAMED | YOUR_TOOL_DESCRIPTION |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have completely distinct purposes: rolling dice, searching the web, and a placeholder tool. There is no overlap in functionality, and each tool's purpose is clearly differentiated from the others.
The naming is inconsistent: 'roll_dice' uses snake_case with a verb-noun pattern, 'web_search' uses snake_case with a noun-verb pattern, and 'YOUR_TOOL_NAME' is a placeholder with a different style. There is no predictable convention across the set.
With only 3 tools, including a placeholder ('YOUR_TOOL_NAME'), the set feels incomplete for a web search server. The scope is unclear, and the tools do not adequately cover typical web search operations beyond a basic search function.
The tool surface is severely incomplete for a web search server. There is only one functional tool ('web_search'), with a dice-rolling tool and a placeholder that do not contribute to the domain. Missing are tools for advanced search, result filtering, or other related operations.