Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

data_uuid_validator

Read-onlyIdempotent

Strictly validate UUID/GUID strings, check RFC version, variant, and special cases like Nil/Max. Supports multiple formats. Extract timestamp for v1/v6/v7. Compare or batch validate up to 1000 at once.

Instructions

UUID / GUID Validator and Parser. Strictly validate a UUID/GUID string and report its structure: validity, RFC 4122 / RFC 9562 version (1-8), variant (NCS, RFC 4122, Microsoft, Reserved), Nil and Max special cases, normalized/uppercase/URN forms, and the embedded timestamp, node, and clock sequence for time-based v1, v6, and v7. Accepts canonical hyphenated, 32-hex no-dash, braced, and urn:uuid: forms. Use this to inspect or verify an existing identifier; use crypto_uuid instead when you need to GENERATE a new UUID. Set operation to validate or identify (single string), compare (test two strings for equality), or batchValidate (up to 1000 strings at once). Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns a result object whose shape depends on the chosen operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoWhich check to run. validate and identify parse one string (field input); compare tests two strings (fields a and b) for equality; batchValidate parses a list (field inputs).
inputNoThe UUID/GUID string to parse. Required for validate and identify. Accepts hyphenated, 32-hex, braced, or urn:uuid: forms; whitespace is trimmed.
aNoFirst UUID string. Required for the compare operation.
bNoSecond UUID string. Required for the compare operation.
inputsNoList of UUID strings to validate in one call. Required for batchValidate; 1 to 1000 items.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request was processed (true on any 200; per-UUID validity is in result).
operationNoThe operation that was run, echoed back.
resultNoOperation-dependent payload. For validate/identify: a single validation object. For compare: equality flags. For batchValidate: counts plus a results array.
Behavior5/5

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

Adds significant context beyond annotations: read-only, non-destructive, local, no external service, rate limit (60 req/min). Consistent with readOnlyHint and idempotentHint annotations.

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?

Well-structured, front-loaded with purpose, then details, alternative, and operations. Every sentence adds value; efficient for the amount of information conveyed.

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?

Comprehensive coverage of purpose, usage, behavior, parameters, operations, safety, and rate limits. No gaps given output schema handles return shape.

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?

Schema coverage is 100%, but description adds operational context (which field for which operation) and acceptable formats. Provides clarity beyond 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 validates and parses UUID/GUID strings, reporting structure and various forms. It distinguishes from crypto_uuid for generation, making purpose unambiguous.

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?

Explicitly states when to use (inspect/verify existing identifier) and when not (generate new one, use crypto_uuid). Also describes operations with their specific inputs.

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/Jambozx/onlinecybertools-mcp-server'

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