Skip to main content
Glama

UK Data: Secure generators

generate_random_string

Read-onlyIdempotent

Generates a random string of specified length from a given character set using a cryptographically secure random source. Returns the generated string. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
lengthNointeger, required, length of the string to generate (must be positive)
charactersNostring, optional, character set to use for generation, default 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior1/5

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

The description adds useful behavior details beyond annotations, including cryptographically secure generation, returned output, and credit cost. However, the idempotentHint=true annotation conflicts with random string generation: repeated calls with identical arguments should not be expected to return the same value.

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 front-loaded with the purpose, then briefly covers return behavior and cost. It is concise and every sentence contributes useful information.

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

Completeness4/5

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

For a two-parameter utility with full schema coverage and annotations, the description covers the generation source, return value, and credit cost. It could clarify non-idempotent behavior and sibling alternatives, but it is otherwise complete.

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 both length and characters are already documented in the schema. The description restates specified length and given character set but adds no parameter-level meaning 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: generates a random string, with scope details such as specified length, given character set, and cryptographically secure source. It distinguishes itself from random number/color generators through the character-set parameter, though it does not explicitly name sibling tools.

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

Usage Guidelines3/5

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

Usage is implied by the purpose, but there is no explicit when-to-use or when-not guidance and no mention of alternatives such as generate_password or generate_username. Adequate for a simple utility, but not strong guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources