AIE8-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. |
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 |
| search_card_by_nameC | Search for a Magic: The Gathering card by name using Scryfall API |
| search_cardsC | Search for Magic: The Gathering cards using Scryfall's search API |
| get_random_cardB | Get a random Magic: The Gathering card from Scryfall |
| get_card_by_idB | Get a specific Magic: The Gathering card by its Scryfall ID |
| get_set_infoC | Get information about a Magic: The Gathering set by its code |
| generate_passwordC | Generate a random password with specified length and character options |
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 8 tools
Most tools have clearly distinct resource/action targets, and the generic utilities are separate from the MTG tools. The only notable overlap is search_card_by_name versus search_cards, since a name query can be expressed as a Scryfall search, but the descriptions provide enough separation.
All names use lowercase snake_case and mostly follow a verb_noun pattern. Minor deviations include web_search (noun_verb) and variation between search_card_by_name and search_cards, but the convention is still predictable.
Eight tools is a well-scoped count for a mixed lookup/utility server. Each tool has a distinct purpose, and there is no obvious bloat or missing obvious companion tool.
The MTG surface covers core read operations: lookup by ID, lookup by name, general search, random card, and set info. Minor gaps include listing/searching sets broadly, card rulings, and set+number lookup, but these are workable around via search or web_search.