AIE7-MCP
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. |
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 |
| check_holidayA | Get holiday information for a specific date and country. Date format: YYYY-MM-DD, Country code: US, CA, GB, etc. |
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 addresses a completely different use case—web search, dice rolling, and holiday lookup—so there is no overlap or confusion between them.
All tool names follow a consistent verb_noun pattern (web_search, roll_dice, check_holiday), making the API predictable and easy to navigate.
With 3 tools, the set is lean but not unreasonably so; however, the tools are unrelated, so the overall scope feels somewhat scattered rather than cohesive, which is why it's not a perfect 5.
The server lacks a clear domain, so completeness is hard to evaluate; while each tool is self-contained, there is no broader workflow that reveals obvious gaps, but also no evidence of comprehensive coverage of a unified purpose.