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

drand-mcp-server

by randa-mu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-randomness-latest

Fetch the current verifiable random value from the drand quicknet. Provides fresh randomness for applications requiring unbiased entropy.

Instructions

Get the latest random value from drand quicknet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-randomness-latest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1-rc1

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, and the description only states the basic action. It does not disclose behavioral traits such as whether the tool is read-only (assumed), if it has any rate limits, or what happens on error. For a tool with no annotations, the description should carry more behavioral context.

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 sentence of 8 words, perfectly sized for the tool's simplicity. It is front-loaded and contains no superfluous information.

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 tool's low complexity (no parameters, simple fetch), the description gives the core idea but lacks details about the output structure. Since there is no output schema, the description could have briefly noted the response format (e.g., round number, randomness value).

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

Parameters4/5

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

The tool has zero parameters, so schema coverage is trivially 100%. The description does not add parameter details because none exist. With no parameters, a baseline of 4 is appropriate as the description does not detract from the schema.

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 action ('Get'), resource ('latest random value'), and source ('drand quicknet'). It distinguishes itself from sibling tools 'get-randomness-by-round' and 'get-randomness-by-time' by focusing on the latest value.

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

Usage Guidelines4/5

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

The description implies usage for obtaining the most recent randomness, but does not explicitly state when to use this tool over siblings or provide exclusions. The context is clear from the name and description, but lacks explicit guidance.

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