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_searchC | Search the web for information about the given query |
| roll_diceC | Roll the dice with the given notation |
| get_stock_ohlcA | Get Open, High, Low, Close (OHLC) data for a stock symbol for the last working day or specified date |
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
Each tool has a completely distinct purpose with no overlap: get_stock_ohlc retrieves financial data, roll_dice performs a random number generation game, and web_search conducts internet queries. The domains are so different that an agent would never confuse them.
The naming is inconsistent with mixed conventions: get_stock_ohlc uses snake_case with a verb_noun pattern, roll_dice uses snake_case but with a verb-only style, and web_search uses snake_case with a noun_verb pattern. There is no predictable naming scheme across the set.
With only 3 tools, the server feels too thin for its apparent scope as a 'Tavily Web Search MCP Server'—web_search aligns with this, but get_stock_ohlc and roll_dice are unrelated utilities that don't fit cohesively. The count is low and the tools lack a unified domain focus.
For a web search server, the surface is severely incomplete: web_search covers basic queries, but there are no tools for advanced search features (e.g., filtering, pagination, or result analysis). The inclusion of unrelated tools like get_stock_ohlc and roll_dice creates gaps in the core domain without adding meaningful coverage.