OnlineCyberTools MCP (280+ filterable tools)

crypto_uuid

Read-only

Generate RFC 4122 UUIDs in version 1 or 4 for identifiers, API keys, or test fixtures. Supports formatting options like hyphens, uppercase, and braces.

Instructions

UUID Generator (v1 and v4). Generate one or more RFC 4122 UUIDs in version 4 (random) or version 1 (timestamp + node), with optional formatting (strip hyphens, uppercase, wrap in braces). Use it to mint fresh identifiers for databases, API keys, or test fixtures; use data_uuid_validator instead to validate or decode an existing UUID. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute anonymous). Output is non-idempotent — each call returns new random values. Returns the canonical and formatted UUID arrays plus the requested version and count.

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

Input Schema

Name	Required	Description
`version`	No	UUID version. 4 = fully random; 1 = time-based (embeds a timestamp and a random node). Only 1 and 4 are supported.
`quantity`	No	How many UUIDs to generate, from 1 to 100.
`formatting`	No	Optional output formatting applied to every generated UUID.

Output Schema

Name	Required	Description	Default
`success`	No	Whether generation succeeded.
`result`	No	The generation payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / formatting / additionalProperties
```
Added value: +false
```

addedInput schema / properties / formatting / description

Added value: +"Optional output formatting applied to every generated UUID."

addedInput schema / properties / formatting / properties / braces / default
```
Added value: +false
```
addedInput schema / properties / formatting / properties / braces / description
```
Added value: +"Wrap each UUID in curly braces, e.g. {550e8400-...}."
```
addedInput schema / properties / formatting / properties / hyphens / default
```
Added value: +true
```

addedInput schema / properties / formatting / properties / hyphens / description

Added value: +"Keep the standard 8-4-4-4-12 hyphens; set false to remove them."

addedInput schema / properties / formatting / properties / uppercase / default
```
Added value: +false
```
addedInput schema / properties / formatting / properties / uppercase / description
```
Added value: +"Emit hex digits in uppercase instead of lowercase."
```

removedInput schema / properties / formatting / required

Removed value: -[
-  "hyphens",
-  "uppercase",
-  "braces"
-]

addedInput schema / properties / quantity / default
```
Added value: +1
```

addedInput schema / properties / quantity / description

Added value: +"How many UUIDs to generate, from 1 to 100."

addedInput schema / properties / quantity / maximum
```
Added value: +100
```
addedInput schema / properties / quantity / minimum
```
Added value: +1
```
addedInput schema / properties / version / default
```
Added value: +4
```

addedInput schema / properties / version / description

Added value: +"UUID version. 4 = fully random; 1 = time-based (embeds a timestamp and a random node). Only 1 and 4 are supported."

addedInput schema / properties / version / enum
```
Added value: +[
+  1,
+  4
+]
```

changedInput schema / required

Previous value: -[
-  "version",
-  "quantity",
-  "formatting"
-]New value: +[]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "The generation payload.",
+      "properties": {
+        "formattedUuids": {
+          "description": "The UUIDs with the requested formatting (hyphens, case, braces) applied.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "quantity": {
+          "description": "Number of UUIDs returned.",
+          "type": "integer"
+        },
+        "rawUuids": {
+          "description": "Canonical lowercase, hyphenated UUID strings.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "version": {
+          "description": "The UUID version generated (1 or 4).",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether generation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds useful context: runs locally, contacts no external service, rate-limited (60/min), and is non-idempotent. No contradictions with annotations.

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 appropriately sized and front-loaded with the core purpose. It covers key details without excessive verbosity. Slight redundancy in mentioning formatting twice, but generally well-structured.

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

Completeness5/5

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

Given the presence of an output schema (implied by description mentioning return arrays), the description covers runtime behavior, rate limits, idempotency, and local execution. It is complete for a straightforward generation tool.

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?

Schema coverage is 100%, with each parameter well-described in the schema. The description adds high-level context (e.g., version 1 is time-based, version 4 random) but does not significantly enhance understanding beyond the schema descriptions.

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 it's a UUID generator for v1 and v4 with optional formatting. It specifies the verb 'Generate' and the resource 'RFC 4122 UUIDs'. This distinguishes it from the sibling tool 'data_uuid_validator' which validates/decodes UUIDs.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('mint fresh identifiers for databases, API keys, or test fixtures') and when not to ('use data_uuid_validator instead to validate or decode an existing UUID'). It also mentions the tool runs locally, is read-only, non-destructive, and rate-limited.

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

Deploy Server