Skip to main content
Glama

TinyFn

by io.tinyfn

random_bytes

Generate cryptographically secure random bytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lengthNoNumber of bytes
encodingNoOutput encoding: hex, base64hex

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bytesYes
valueYes
encodingYes

Schema Changelog

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

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

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden, but the description only states the cryptographic security property. It doesn't disclose the output format, the relationship between length and encoding, whether the output is returned as a string, or any binary-decoding behavior. The term 'cryptographically secure' is a useful security property, but the overall behavioral disclosure is minimal for a tool that has multiple behavioral dimensions.

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?

One short, front-loaded sentence that conveys the core security property. It wastes no words and is easy to parse. It could add a bit more context without becoming verbose, but as-is it is appropriately sized for a simple 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?

Given an output schema exists and both parameters are fully documented, the description is adequate for a basic random-byte generator. However, it lacks any indication of when to choose cryptographically secure bytes over other random tools, and it doesn't mention potential security implications or alternatives. It is minimally complete, not richly contextual.

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%, so the schema already documents both parameters ('Number of bytes' and 'Output encoding: hex, base64'). The description adds no additional meaning beyond the schema. Baseline 3 applies because the schema does the heavy lifting; the description's mention of 'random bytes' doesn't add parameter-level insight.

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 'Generate cryptographically secure random bytes.' states a clear verb and resource, and the cryptographic security qualifier distinguishes it from generic random generators. However, the tool name 'random_bytes' is essentially a synonym for the description, so it doesn't strongly differentiate from sibling tools like 'lorem_bytes', 'random_hex', or 'random_bytes_2'.

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 guidance is given for when to use this tool vs alternatives. The description says 'cryptographically secure', which implies use for security-sensitive random generation, but it does not explicitly mention alternatives like random_bytes_2, random_hex, or random_string, nor does it state exclusion conditions. Given the large sibling list, this is a missed opportunity.

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