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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
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 |
| stock_infoC | Get consolidated stock information about a stock TICKER |
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 targets a completely different domain: dice rolling, stock info, and web search. There is no overlap or ambiguity between them.
All names use snake_case, but 'roll_dice' follows a verb_noun pattern while 'stock_info' and 'web_search' are noun_noun. This is a minor inconsistency but still readable.
With 3 tools, the set is small but still feels reasonable for a general-purpose utility server. It is not excessively thin for the apparent scope.
The tools cover three unrelated functionalities with no common domain. There is no coverage of typical CRUD or lifecycle operations, and the set seems arbitrarily assembled without a clear purpose.