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 |
| repair_costC | Get repair cost estimate for home repairs |
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: home repair cost estimation, dice rolling, and web searching. There is no overlap in functionality, and an agent would have no difficulty selecting the correct tool for any given task.
The naming is inconsistent with mixed conventions: 'repair_cost' and 'web_search' follow a noun_verb pattern, while 'roll_dice' uses verb_noun. This lack of a predictable naming pattern could cause confusion in automated tool selection.
With only three tools, the server appears severely under-scoped for a 'Tavily Web Search MCP Server', as web search is just one of three unrelated functions. The tools do not form a coherent set for the stated server purpose.
For a web search server, the tool surface is severely incomplete, lacking essential operations like advanced search filters, result pagination, or domain-specific searches. The inclusion of unrelated tools (repair_cost, roll_dice) further fragments the domain coverage.