drand-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-randomness-latestA | Get the latest random value from drand quicknet |
| get-randomness-by-roundC | Get the random value associated with a specfic round from drand quicknet |
| get-randomness-by-timeA | Get the random value associated with a specific time from drand quicknet |
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 requires a distinct input: round number, timestamp, or no input for latest. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tool names follow the consistent pattern 'get-randomness-by-{criteria}', using hyphenated lowercase. The naming is predictable and clear.
Three tools is appropriate for a focused server that retrieves randomness from drand. The count is not excessive nor insufficient for the domain.
The tools cover the primary ways to fetch randomness (by round, by time, latest). One could argue for a tool to list available rounds, but the current set is functionally complete for the server's purpose.