Fortune MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| draw_tarotB | タロットカードを引いて占い結果を返します |
| get_horoscopeB | ホロスコープを計算して返します |
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 2 tools
The two tools have completely distinct purposes with no overlap. draw_tarot provides tarot card readings, while get_horoscope calculates astrological horoscopes. An agent would never confuse these tools as they serve different divination methods.
Both tools follow a consistent verb_noun pattern with clear, descriptive names. draw_tarot and get_horoscope use the same naming convention throughout, making them predictable and easy to understand.
With only 2 tools, this server feels quite thin for a fortune-telling domain. While tarot and horoscope are distinct, other common divination methods (like numerology, palm reading, or I Ching) are missing. The scope feels incomplete with just these two offerings.
For a fortune-telling server, the surface is severely incomplete. While tarot and horoscope are covered, there are significant gaps in the domain - no general fortune-telling, no compatibility readings, no prediction tools, and no way to interpret or combine results from different methods.