Skip to main content
Glama
zazencodes

Random Number MCP

by zazencodes

secure_random_int

Generate a cryptographically secure random integer between 0 and a specified upper bound (exclusive).

Instructions

Generate a secure random integer below upper_bound.

Args: upper_bound: Upper bound (exclusive)

Returns: Random integer in range [0, upper_bound)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upper_boundYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core implementation of secure_random_int. Uses secrets.randbelow() to generate a cryptographically secure random integer in [0, upper_bound). Validates upper_bound is a positive integer.
    def secure_random_int(upper_bound: int) -> int:
        """Generate a secure random integer below upper_bound.
    
        Args:
            upper_bound: Upper bound (exclusive)
    
        Returns:
            Random integer in range [0, upper_bound)
    
        Raises:
            ValueError: If upper_bound <= 0
            TypeError: If upper_bound is not an integer
        """
        if not isinstance(upper_bound, int):
            raise TypeError("upper_bound must be an integer")
    
        if upper_bound <= 0:
            raise ValueError("upper_bound must be positive")
    
        return secrets.randbelow(upper_bound)
  • MCP tool registration wrapper for secure_random_int. Decorated with @app.tool() to expose it as an MCP tool. Delegates to tools.secure_random_int().
    @app.tool()
    def secure_random_int(upper_bound: int) -> int:
        """Generate a secure random integer below upper_bound.
    
        Args:
            upper_bound: Upper bound (exclusive)
    
        Returns:
            Random integer in range [0, upper_bound)
        """
        return tools.secure_random_int(upper_bound)
  • Registration of secure_random_int as an MCP tool via the @app.tool() decorator on the server handler function.
    @app.tool()
    def secure_random_int(upper_bound: int) -> int:
        """Generate a secure random integer below upper_bound.
    
        Args:
            upper_bound: Upper bound (exclusive)
    
        Returns:
            Random integer in range [0, upper_bound)
        """
        return tools.secure_random_int(upper_bound)
  • Input schema defined by the type hint 'upper_bound: int' in the tool registration, which FastMCP uses to generate the JSON schema for the tool.
    def secure_random_int(upper_bound: int) -> int:
        """Generate a secure random integer below upper_bound.
    
        Args:
            upper_bound: Upper bound (exclusive)
    
        Returns:
  • Utility functions used by tools.py (validate_range, validate_positive_int, etc.) — though secure_random_int does its own inline validation rather than using these helpers.
    """Utility functions for the random number MCP server."""
    
    from typing import Any
    
    
    def validate_range(low: int | float, high: int | float) -> None:
        """Validate that low <= high for range-based functions."""
        if low > high:
            raise ValueError(f"Low value ({low}) must be <= high value ({high})")
    
    
    def validate_positive_int(value: int, name: str) -> None:
        """Validate that a value is a positive integer."""
        if not isinstance(value, int):
            raise TypeError(f"{name} must be an integer, got {type(value).__name__}")
        if value < 0:
            raise ValueError(f"{name} must be non-negative, got {value}")
    
    
    def validate_list_not_empty(items: list[Any], name: str) -> None:
        """Validate that a list is not empty."""
        if not items:
            raise ValueError(f"{name} cannot be empty")
    
    
    def validate_weights_match_population(
        population: list[Any], weights: list[int | float]
    ) -> None:
        """Validate that weights list matches population length."""
        if len(weights) != len(population):
            raise ValueError(
                f"Weights list length ({len(weights)}) must match "
                f"population length ({len(population)})"
            )
Behavior3/5

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

With no annotations, the description must disclose behavior. It states 'secure' (suggesting cryptographic randomness) and defines the output range. However, it does not explain security implications or constraints (e.g., upper_bound must be positive). It is adequate but not comprehensive.

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?

Two sentences with clear purpose and parameter description. Front-loaded with the main action. No wasted words.

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

Completeness4/5

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

For a simple tool with an output schema, the description covers its own behavior and parameters well. However, it lacks guidance on when to use this tool over siblings, slightly reducing completeness.

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

Parameters5/5

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

The schema has 0% parameter coverage, so the description fully compensates by explaining 'upper_bound: Upper bound (exclusive)', adding critical meaning beyond the schema's raw type.

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 'Generate' and the resource 'secure random integer', with the constraint 'below upper_bound'. This precisely distinguishes it from sibling tools like random_int, which may not emphasize security.

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 on when to use this tool over alternatives like random_int or random_float. The description does not provide context or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zazencodes/random-number-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server