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 |
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 |
| scientific_calculatorA | Evaluate mathematical expressions using a scientific calculator. Supports:
Examples:
|
| generate_qr_codeB | Generate a QR code for the given data. Args: data: The text or URL to encode in the QR code error_correction: Error correction level - "L" (Low ~7%), "M" (Medium ~15%), "Q" (Quartile ~25%), "H" (High ~30%) border: Size of the border (minimum is 4) box_size: Size of each box in pixels (default 10) Returns: Base64 encoded PNG image of the QR code that can be displayed or saved |
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 4 tools
Each tool serves a completely distinct purpose with no overlap: QR code generation, dice rolling, scientific calculation, and web search. An agent can easily differentiate between these unrelated functionalities, eliminating any risk of misselection.
Three tools follow a consistent verb_noun pattern (generate_qr_code, roll_dice, web_search), but 'scientific_calculator' deviates as a noun_noun compound. This minor inconsistency slightly reduces predictability, though the names remain clear and readable.
With only 4 tools, the set feels thin for a server named 'Tavily Web Search MCP Server', as web search is just one component among unrelated utilities. The count is borderline—too few to fully cover a coherent domain, suggesting a miscellaneous toolkit rather than a focused service.
For a web search server, the toolset is severely incomplete, lacking essential operations like filtering results, pagination, or retrieving specific content. The inclusion of unrelated tools (QR code, dice, calculator) further dilutes the domain, creating significant gaps that will hinder agent workflows focused on search.