Skip to main content
Glama
Sign In
drand-mcp-server

drand-mcp-server

by randa-mu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-randomness-by-time

Retrieve a verifiable random beacon from the drand network by inputting a Unix timestamp.

Instructions

Get the random value associated with a specific time from drand quicknet

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "time": "<time>"
    },
    "name": "get-randomness-by-time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1-rc1

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It only states that it retrieves a random value but does not disclose potential errors, uniqueness constraints, or output format. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that conveys the purpose without extra words. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool (one parameter, no output schema), the description is partially complete. It lacks detail on parameter format and return value, but covers the basic purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. However, it only loosely refers to 'a specific time' without explaining the format (Unix timestamp, milliseconds, etc.) or the unit of the number parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Get), the resource (random value), and the context (associated with a specific time from drand quicknet). It effectively distinguishes this tool from its siblings (by-round and latest) by specifying 'by time'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the context implies use when you have a specific time, there is no explicit guidance on when to use this tool over alternatives, nor any prerequisites or limitations mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools