Random Number MCP

random_shuffle

Randomize the order of items in a list by returning a new shuffled list.

Instructions

Return a new list with items in random order.

Args: items: List of items to shuffle

Returns: New list with items in random order

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": {
      "items": "<items>"
    },
    "name": "random_shuffle"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.0May 2, 2026

addedInput schema / properties / items / items / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / items / title
```
Removed value: -"Items"
```

addedOutput schema / description

Added value: +"Generic wrapper for non-object return types."

addedOutput schema / properties / result / items / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"_WrappedResult"
```

First observedv1.0.0Aug 15, 2025

TDQS

A3.6/5.0

Behavior3/5

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

The description discloses that the operation returns a new list (non-destructive) and uses random order, but lacks details about randomness quality (e.g., cryptographic vs. pseudo-random) or performance implications. With no annotations, the description provides basic transparency but could be more informative.

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 extremely concise: two sentences plus standard args/returns docstring. Every sentence is necessary, with no redundant or irrelevant information. Well-structured for quick consumption.

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 (one parameter, straightforward purpose), the description covers the essential behavior. It states the return type and action. The presence of an output schema (not shown) likely completes the contract, so the description is adequate.

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

Parameters3/5

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

The description adds marginal value beyond the input schema by labeling 'items' as a 'List of items to shuffle.' Schema coverage is 0%, but the single-parameter simplicity and clear docstring compensate somewhat. However, no additional constraints or example formats are provided.

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 'Return a new list with items in random order,' specifying the verb ('return'), resource ('list'), and operation ('random order'). It distinguishes from siblings like random_choices and random_sample by focusing on shuffling the entire list, not sampling.

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 usage guidance is provided. The description does not indicate when to use this tool over alternatives like random_choices or random_sample, nor does it mention any prerequisites or exclusions.

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

Deploy Server