Skip to main content
Glama

TinyFn

by io.tinyfn

random_bytes_2

Generate cryptographically secure random bytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format: hex, base64, urlsafehex
lengthNoNumber of bytes to generate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bytesYes
valueYes
formatYes
secureYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__random_utils__RandomBytesResponse"New value: +"RandomBytesResponse"
  2. Changed3 schema fields changed
    • removedOutput schema / $defs / RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"RandomBytesResponse"New value: +"app__routers__random_utils__RandomBytesResponse"
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__random_utils__RandomBytesResponse"New value: +"RandomBytesResponse"
  4. Changed3 schema fields changed
    • removedOutput schema / $defs / RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"RandomBytesResponse"New value: +"app__routers__random_utils__RandomBytesResponse"
  5. Changed3 schema fields changed
    • addedOutput schema / $defs / RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • removedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"app__routers__random_utils__RandomBytesResponse"New value: +"RandomBytesResponse"
  6. Changed3 schema fields changed
    • removedOutput schema / $defs / RandomBytesResponse
      Removed value: -{
-  "properties": {
-    "bytes": {
-      "title": "Bytes",
-      "type": "integer"
-    },
-    "format": {
-      "title": "Format",
-      "type": "string"
-    },
-    "secure": {
-      "title": "Secure",
-      "type": "boolean"
-    },
-    "value": {
-      "title": "Value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "value",
-    "bytes",
-    "format",
-    "secure"
-  ],
-  "title": "RandomBytesResponse",
-  "type": "object"
-}
    • addedOutput schema / $defs / app__routers__random_utils__RandomBytesResponse
      Added value: +{
+  "properties": {
+    "bytes": {
+      "title": "Bytes",
+      "type": "integer"
+    },
+    "format": {
+      "title": "Format",
+      "type": "string"
+    },
+    "secure": {
+      "title": "Secure",
+      "type": "boolean"
+    },
+    "value": {
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "bytes",
+    "format",
+    "secure"
+  ],
+  "title": "RandomBytesResponse",
+  "type": "object"
+}
    • changedOutput schema / x-fastmcp-top-level-schema
      Previous value: -"RandomBytesResponse"New value: +"app__routers__random_utils__RandomBytesResponse"
  7. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does communicate a key behavioral trait—that the bytes are cryptographically secure—which is valuable context. However, it does not mention any other behavior such as return format flexibility, length constraints, or non-determinism, though the schema covers some of these.

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 a single declarative sentence with zero wasted words. It front-loads the key differentiator ('cryptographically secure') and is appropriately sized for a simple utility tool.

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 two-parameter tool with a complete schema and an output schema, the description is nearly sufficient to call it correctly. The main missing element is contextual guidance on its relationship to the sibling 'random_bytes', which could lead to incorrect tool selection. Still, the essential operational details are present.

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 description coverage is 100%, with both 'format' and 'length' having clear descriptions in the schema itself. The tool description adds no parameter-specific meaning, but given the schema's completeness, the baseline of 3 is appropriate.

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?

The description clearly states the action ('Generate') and the resource ('cryptographically secure random bytes'). It differentiates from most other random generation tools by emphasizing cryptographic security, but it does not explicitly distinguish itself from its direct sibling 'random_bytes', leaving some ambiguity.

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?

The description gives no guidance on when to use this tool versus alternatives like 'random_bytes' or other random generators. There is no mention of use cases, contexts, or exclusion criteria, so an agent cannot determine why this tool should be chosen over its siblings.

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

All TinyFn toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple random generators (random_integer, random_number), duplicate hashing functions (hash_md5, md5_checksum), and near-identical tools (compare, compare_2, compare_decimals). The sheer number of tools and lack of clear boundaries make it difficult for an agent to differentiate.

Naming Consistency1/5

Naming is highly inconsistent. There are duplicate tools with different names (camel_case vs to_camel_case, slug vs slugify), arbitrary suffixes like '_2', and mixing of patterns (e.g., generate_password vs password_entropy). No clear convention is followed.

Tool Count1/5

With 572 tools, the server is massively overpopulated for any coherent purpose. It includes trivial endpoints (true_endpoint, null, hello_world) and numerous duplicates, far exceeding a well-scoped utility set.

Completeness2/5

While the server covers many domains (math, strings, dates, colors, etc.), the presence of duplicate and trivial tools indicates a lack of thoughtful curation. There are gaps in basic operations (e.g., no dedicated file or network tools), and many tools are redundant.

Resources