MCP Lottery Demo
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_lotteryB | 从给定的选项列表中随机抽取一个或多个结果 |
| roll_diceC | 投掷骰子，支持自定义面数和数量 |
| flip_coinB | 抛硬币，返回正面或反面 |
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 clearly distinct purpose: draw_lottery selects from a list of options, flip_coin returns heads or tails, and roll_dice handles dice with customizable faces and counts. There is no overlap or ambiguity between these random selection mechanisms.
All tools follow a consistent verb_noun pattern (draw_lottery, flip_coin, roll_dice) with clear, descriptive names that accurately reflect their functions. The naming is uniform and predictable throughout the set.
With 3 tools, the server is well-scoped for a lottery/gambling demo, covering common random selection scenarios (lottery draws, coin flips, dice rolls). Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides complete coverage for basic random selection operations in a gambling context: drawing from options, binary coin flips, and customizable dice rolls. There are no obvious gaps for the stated demo purpose, and agents can handle typical use cases without dead ends.