Random-Generator

generate_random_boolean

generate_random_boolean

Generate cryptographically secure random boolean values for applications requiring high-quality randomness, with configurable count and probability parameters.

Instructions

Generate cryptographically secure random boolean values

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": "generate_random_boolean"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No
`probability`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 5, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'cryptographically secure', which adds some behavioral context about security, but fails to disclose other traits like performance, error handling, or output format. For a tool with parameters, this is insufficient to guide effective use.

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, efficient sentence with no wasted words. It's appropriately sized and front-loaded, directly stating the core functionality without unnecessary elaboration.

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?

Given the complexity (two parameters, no annotations, no output schema), the description is incomplete. It lacks parameter explanations, usage context, and details on return values, making it inadequate for an agent to reliably invoke this tool without guesswork.

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. It doesn't explain the 'count' or 'probability' parameters at all, leaving their purpose and effects undocumented. This is a significant gap given the two parameters and low schema coverage.

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

Purpose4/5

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

The description clearly states the verb ('generate') and resource ('cryptographically secure random boolean values'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'generate_random_choice' or 'generate_random_integer', which could also produce boolean-like outputs, so it doesn't achieve full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where boolean generation is preferred over other random generation tools, nor does it specify prerequisites or exclusions, leaving usage context ambiguous.

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

Deploy Server