Skip to main content
Glama

Generate usernames and stream names

generate_names
Read-only

Generate random name ideas that already follow the platform's username rules (length, allowed characters, underscores): Twitch channel names, generic gamertags, Minecraft, Roblox, Discord usernames, Discord server names, Fortnite (Epic) display names, Valorant Riot IDs, Xbox gamertags and clan names with tags. Use it when the user asks for name ideas; offer to generate more or switch style. Availability is not checked: use check_username for Minecraft or Roblox.

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": {
      "platform": "<platform>"
    },
    "name": "generate_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many names to return.
styleNoVibe of the names: gamer (Gamer), cute (Cute & cozy), dark (Dark & edgy), funny (Funny), fantasy (Fantasy), minimal (Minimal / pro), sweaty (Sweaty / competitive), blocky (Blocky / crafting), clan (Clan / team), community (Community). Each platform supports a subset; defaults to its first style.
keywordNoOptional word to build names around, e.g. the user's nickname or favourite game character (letters and numbers only).
numbersNoAllow numbers at the end of some names.
platformYesWhere the name will be used. "gamertag" works on most platforms.
max_lengthNoOptional maximum length; capped at the platform maximum.
separatorsNoAllow separators such as _ or spaces where the platform permits them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description only needs to add nuance. It does: names are randomly generated (consistent with idempotentHint=false), they already obey platform rules for length/characters/underscores, and critically, availability is NOT verified — a behavioral caveat an agent could not infer from annotations alone. It stops short of describing the returned shape, which keeps it off a 5.

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?

Two dense sentences, front-loaded with the core action and platform list, then usage guidance and the check_username caveat. The platform enumeration is long but functional rather than filler; there is little wasted wording.

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?

Seven parameters with full schema coverage need little prose support, and the description supplies scope, constraints, and the availability caveat. The only gap is that it never indicates what the tool returns (presumably a list of generated names), which an agent might want before calling.

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 every parameter including count, style, keyword, numbers, max_length, and separators is already documented with enums, defaults, and bounds. The description only restates platform-level constraints (length, allowed characters, underscores), adding no syntax or semantics beyond the schema. Baseline 3 applies.

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?

Names a specific verb and resource ('Generate random name ideas') and enumerates the concrete outputs (Twitch channel names, Discord server names, Xbox gamertags with tags) so it's unmistakably distinct from siblings like check_username or get_stream_settings.

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 it ('when the user asks for name ideas'), suggests follow-up behavior ('offer to generate more or switch style'), and routes the agent elsewhere for a related need ('Availability is not checked: use check_username for Minecraft or Roblox'). This is a clear when/when-not/alternative triad.

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