Skip to main content
Glama
zazencodes

Random Number MCP

by zazencodes

random_sample

Randomly select k unique items from a provided list without replacement, ensuring no duplicates.

Instructions

Choose k unique items from population without replacement.

Args: population: List of items to choose from k: Number of items to choose

Returns: List of k unique chosen items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
populationYes
kYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core implementation of random_sample: chooses k unique items from population without replacement using random.sample(). Validates inputs via validate_list_not_empty, validate_positive_int, and checks k <= len(population).
    def random_sample(population: list[Any], k: int) -> list[Any]:
        """Choose k unique items from population without replacement.
    
        Args:
            population: List of items to choose from
            k: Number of items to choose
    
        Returns:
            List of k unique chosen items
    
        Raises:
            ValueError: If population is empty, k < 0, or k > len(population)
            TypeError: If k is not an integer
        """
        validate_list_not_empty(population, "population")
        validate_positive_int(k, "k")
        if k > len(population):
            raise ValueError("Sample size k cannot be greater than population size")
        return random.sample(population, k)
  • Registers random_sample as an MCP tool via @app.tool() decorator. Defines the public schema with typed parameters (population: list, k: int) and delegates to tools.random_sample().
    @app.tool()
    def random_sample(
        population: list[str | int | float | bool], k: int
    ) -> list[str | int | float | bool]:
        """Choose k unique items from population without replacement.
    
        Args:
            population: List of items to choose from
            k: Number of items to choose
    
        Returns:
            List of k unique chosen items
        """
        return tools.random_sample(population, k)
  • Input schema for random_sample: population as list[str|int|float|bool] and k as int. Returns list[str|int|float|bool].
    def random_sample(
        population: list[str | int | float | bool], k: int
    ) -> list[str | int | float | bool]:
        """Choose k unique items from population without replacement.
    
        Args:
            population: List of items to choose from
            k: Number of items to choose
    
        Returns:
            List of k unique chosen items
        """
        return tools.random_sample(population, k)
  • validate_positive_int helper: validates that k is an integer and non-negative, used by random_sample handler.
    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}")
  • validate_list_not_empty helper: validates that population list is not empty, used by random_sample handler.
    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")
Behavior4/5

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

With no annotations, the description carries the full burden. It explains the output (list of k unique items) and the without-replacement behavior. It does not mention error conditions like k > population size, but for a simple random sample this is acceptable.

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 concise with 5 lines, structured cleanly with Args and Returns sections, no unnecessary 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?

Given the tool's simplicity and the presence of an output schema (though not shown), the description is largely complete. It covers purpose, parameters, and return value. A slight gap is not mentioning the error case when k > population size.

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 description adds meaning to both parameters beyond the bare schema: 'population: List of items to choose from' and 'k: Number of items to choose'. This compensates for the 0% schema coverage. However, it could be more explicit about constraints (e.g., k must be <= length of population).

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 'choose' and the resource 'k unique items from population without replacement', which is specific and distinguishes from the sibling 'random_choices' which likely does with replacement.

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?

The description implies when to use (when without replacement) but does not explicitly state when not to use or compare to alternatives like 'random_choices' for with-replacement sampling.

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