Coin Flip 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 |
|---|---|
| flip_coinB | Flip a coin with n sides using true randomness from random.org. For 3-sided coins, try creative side names like:
Meta-usage patterns:
Ordinal Meta-patterns:
Default ternary values are -/0/+ |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'flip_coin' has a single, clearly defined purpose.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'flip_coin' follows a clear verb_noun pattern.
A single tool is too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. While the tool is versatile, the server would benefit from additional tools to support more complex operations.
The server's domain appears to be random generation or decision-making, but with only one tool, there are significant gaps. For example, there are no tools for setting parameters, retrieving results, or managing multiple flips in a structured way, which limits agent workflows.