Character names from five generators: cyberpunk, Elden Ring, druid, Baldur's Gate 3, Pokémon.
Scored across 2 tools
The two tools have clearly distinct purposes: one generates names, the other lists available generators and settings. An agent can easily tell when to use each without overlap.
Both tools follow a consistent verb_noun snake_case pattern: generate_names and list_name_generators. The convention is predictable and readable.
Two tools is thin for a server that supports five distinct name generators, though the generate_names tool absorbs all genres via parameters. It is functional but borderline minimal.
The surface covers discovery and generation well, including settings and links. Minor gaps exist, such as no separate preset retrieval or dedicated naming-guide tool, but agents can work around them.
Use this when the user wants name ideas for a character in one of five genres: cyberpunk (aliases, hacker handles, corporate cover names), elden-ring (dark-fantasy names, optionally with an epithet), druid (nature names and surnames for D&D and fantasy games), baldurs-gate-3 (custom character names by ancestry: human, elf, dwarf, tiefling, halfling), pokemon (nicknames and invented creature names). Returns up to 12 names from the generator’s word banks, the settings used and a link to the generator page. Styles and formats per generator: cyberpunk (Cyberpunk Name Generator): style runner | hacker | fixer | corporate; format full | short. elden-ring (Elden Ring Name Generator): style knight | scholar | wanderer | mystic; format full | short | title. druid (Druid Name Generator): style woodland | moon | storm | wildfire; format full | short | surname. baldurs-gate-3 (Baldur’s Gate 3 Name Generator): style human | elf | dwarf | tiefling | halfling; format full | short. pokemon (Pokémon Name Generator): style grass | fire | water | electric | ice | ghost; format short | compound.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Optional: the same seed and settings give the same batch again. Default: random. | |
| count | No | How many names (1–12). | |
| style | No | The generator’s theme (its word bank), e.g. "hacker" for cyberpunk, "tiefling" for baldurs-gate-3, "fire" for pokemon. Default: the generator’s default. | |
| format | No | Name format, e.g. "full" (name + byname), "short" (single name), "surname" (druid), "title" (elden-ring: name, epithet), "compound" (pokemon: invented creature name). Default: the generator’s default. | |
| generator | Yes | Which generator: cyberpunk, elden-ring, druid, baldurs-gate-3 or pokemon. | |
| max_length | No | Character limit, counting spaces and punctuation (4–40), e.g. a game’s name-length limit. Default: the generator’s default (12 or 24). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantive behavior beyond them: it returns up to 12 names plus the settings used and a link to the generator page. It does not cover failure modes (e.g. an invalid style for a given generator), which keeps it below 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The usage condition is correctly front-loaded, but the second half is padded by repeating each generator as '(Cyberpunk Name Generator)', '(Elden Ring Name Generator)', etc., which adds no information. The style/format enumeration earns its place; the parenthetical restatements do not.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description usefully states what comes back (names, settings used, generator link), and it documents the generator-specific style/format vocabularies. Only the behavior on invalid or mismatched style values is left unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so a 3 would be the baseline, but the description goes further by enumerating the valid style and format values per generator (e.g. cyberpunk style runner|hacker|fixer|corporate, format full|short; pokemon format short|compound). That is real meaning the free-string schema fields do not supply.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence gives a specific verb+resource (generate name ideas for a character) and enumerates the five generator domains, which immediately separates it from the sibling list_name_generators. An agent can tell exactly which requests belong here without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The opening 'Use this when the user wants name ideas for a character in one of five genres' gives a clear triggering condition and genre scoping. It stops short of naming the sibling tool as the alternative for discovery/enumeration, so it is clear context rather than a full when/when-not routing rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Lists the five name generators with their styles, formats, defaults, ready-made presets, page links and naming guides. Use it when the user wants to know what the generators offer or which settings to pick.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful detail about the returned content (styles, formats, defaults, presets, page links, guides), though it does not describe response structure or ordering.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences with no filler. The primary action and returned content are front-loaded before the usage guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only listing tool with annotations covering safety, the description gives an agent everything needed: what it lists, what details are included, and when to use it. No output schema exists, but the returned content is described.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, and the description correctly focuses on what the listing returns. No parameter semantics are needed, so this is near-baseline strong.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Lists the five name generators') and enumerates what is included: styles, formats, defaults, presets, page links, and naming guides. The listing purpose is clearly distinct from the sibling generate_names tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly gives the use case: when the user wants to know what the generators offer or which settings to pick. It does not explicitly name generate_names as the alternative for actually producing names, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
generate_nameslist_name_generatorsCharacters, campaigns, adventures & worlds for D&D 5e/5.5e, Pathfinder, Savage Worlds, Fate, & more.
Generate fictional names and sample identity profiles for prototypes, QA, demos, and creative work.
Original instrumental songs from words, each with five stems. Royalty-free, for games and videos.
random-tables — Pipeworx original composable random tables for tabletop and narrative play…
Add one secure layer between your agents and this server.
