GadgetHumans API Hub

uuid

Generate fresh random UUID v4 identifiers, one or many in a single call - cryptographically random and instant.

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": {
      "count": "<count>"
    },
    "name": "uuid"
  }
}

Input Schema

Name	Required	Description	Default
`count`	Yes	Number of UUIDs to generate (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / count

Added value: +{
+  "description": "Number of UUIDs to generate (default 1)",
+  "type": "integer"
+}

addedInput schema / required
```
Added value: +[
+  "count"
+]
```

AddedNov 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations supplied, the description does carry useful behavioural facts: output is cryptographically random, generation is instant, and batching is supported. It omits the one thing that matters for correct consumption — whether a count greater than 1 yields an array or a delimited string — and whether count is capped.

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?

A single front-loaded sentence with zero padding; the core action comes first and the qualifiers follow. Nothing here could be cut without losing information.

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

Completeness3/5

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

For a one-parameter, non-destructive utility this is close to sufficient, but without an output schema the description should say what the return value looks like for multi-count calls. Absent that, an agent must guess whether to index or split the result.

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% and the 'count' parameter already documents its type and default of 1. The description's 'one or many in a single call' reinforces the batching semantics but adds no format, range, or boundary information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus the exact variant ('Generate fresh random UUID v4 identifiers'), so an agent knows precisely what comes back. It does not, however, distinguish this from the sibling tool 'generate_uuid', which sounds functionally identical.

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?

There is no guidance on when to pick this over the near-duplicate sibling 'generate_uuid', or over adjacent identifier tools like 'nanoid' and 'ulid'. The only hint is 'one or many in a single call', which implies batch use but is framed as a capability rather than a selection criterion.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.