Tavily 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 |
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_searchC | 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 clearly distinct purposes with no overlap: roll_dice handles random number generation, web_search performs internet queries, and YOUR_TOOL_NAME (though placeholder) appears to be a distinct third function. Each tool targets a completely different domain, making misselection unlikely.
Naming conventions are inconsistent: roll_dice uses snake_case with a verb_noun pattern, web_search also uses snake_case verb_noun, but YOUR_TOOL_NAME uses a different style (all caps with underscores). While two tools follow a pattern, the third breaks it completely, creating naming chaos.
With only three tools, this feels thin for a 'Tavily Search MCP Server' - the name suggests search-focused functionality, but only one tool (web_search) directly supports this. The inclusion of dice rolling seems out of scope, making the tool count borderline appropriate but poorly aligned with the server's stated purpose.
For a search server, there are significant gaps: only basic web_search is provided, with no advanced search options, filtering, result processing, or search history management. The placeholder tool and dice rolling don't address core search functionality, leaving the surface incomplete for search-related workflows.