Drand
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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 |
|---|---|
| get-randomness-latestB | 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-timeC | 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 has a clearly distinct purpose with no overlap: get-randomness-by-round retrieves randomness for a specific round, get-randomness-by-time for a specific time, and get-randomness-latest for the most recent value. The descriptions explicitly differentiate the input parameters (round, time, latest), making it impossible to confuse them.
All tool names follow a consistent verb_noun pattern with hyphens: 'get-randomness-by-round', 'get-randomness-by-time', and 'get-randomness-latest'. This uniformity makes the naming predictable and easy to understand, adhering to a clear convention throughout the set.
With 3 tools, the count is appropriate for the server's purpose of fetching randomness from drand quicknet, as it covers the main use cases (by round, by time, latest). It is slightly lean but reasonable, as adding more tools might overcomplicate this focused domain without obvious gaps.
The tool set provides complete coverage for retrieving randomness values from drand quicknet, addressing key scenarios: specific rounds, specific times, and the latest value. A minor gap might be the lack of tools for metadata or chain information, but for the core functionality of fetching randomness, it is nearly complete and functional.