AIE8-MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key. | |
| TAVILY_API_KEY | Yes | A valid Tavily API key for web search capabilities. | |
| WEATHER_API_KEY | Yes | Your WeatherAPI key from https://www.weatherapi.com/, used for weather-related queries. |
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_searchB | Search the web for information about the given query |
| roll_diceC | Roll the dice with the given notation |
| get_weatherC | Get the weather for the given location |
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 (weather, dice rolling, web search) with no overlap, making it easy for an agent to select the correct one.
All tool names follow the consistent verb_noun pattern (get_weather, roll_dice, web_search) without any mixing of conventions.
With 3 tools, the count is appropriate for a focused utility server; each tool is distinct and earns its place.
The tool set lacks a coherent domain—it's a random collection of unrelated functions (weather, dice, search) with obvious gaps for a general-purpose assistant (e.g., no calendar, math, or storage tools).