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

drand-mcp-server

by randa-mu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-randomness-by-round

Retrieve the verifiable random value associated with a given round number from the drand quicknet network.

Instructions

Get the random value associated with a specfic round 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": {
      "round": "<round>"
    },
    "name": "get-randomness-by-round"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1-rc1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Get', implying a read operation, but does not disclose any side effects, error behavior, authentication needs, or what happens for invalid rounds. Minimal behavioral info.

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

Conciseness4/5

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

The description is a single sentence with no wasted words. However, there is a typo ('specfic' instead of 'specific'), which slightly reduces clarity.

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

Completeness2/5

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

For a simple tool with one parameter and no output schema, the description should explain what 'round' means and what the return value is. It does not mention that 'drand quicknet' is a specific network or describe the output format. Incomplete.

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 coverage is 0% (parameter has no description). The description only implies the 'round' parameter via the resource name but does not explain its meaning, format, or constraints. Does not compensate for the lack of schema detail.

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 'Get the random value associated with a specific round from drand quicknet', which includes a verb and specific resource. It distinguishes from siblings ('get-randomness-by-time' and 'get-randomness-latest') by specifying input is a round.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus the siblings. The description does not mention alternatives or conditions for usage.

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