Skip to main content
Glama

AvatarSay

Roll Tabletop RPG / D&D NPC + VTT Exports

roll_rpg_npc
Read-onlyIdempotent

Deterministically roll a complete tabletop RPG / D&D NPC (name, ancestry, role, traits, quirk, plot hook, GM secret, portrait prompt, matched voice sample MP3, and a <=75-char greeting tuned for the free 5s talking video clip), plus ready-to-import SillyTavern Character Card V2 JSON and Foundry VTT NPC Actor JSON. Public zero-cost tool — requires NO API key and charges 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
roleNoOptional tabletop role filter or custom archetype, e.g. "Tavern keeper", "Runesmith", "Hedge alchemist", "Harbor smuggler", "Wandering bard".
seedNoOptional deterministic seed (e.g. "forge26a" or "42"). Same seed always produces the exact same NPC; omit to roll a fresh random seed.
styleNoVisual portrait style preset (default "fantasy"). Supports fantasy, anime, 3d-cartoon (or aliases cartoon / 3d), pixel-art, cyberpunk, watercolor, realistic, professional-headshot.
genderNoOptional character presentation filter: "f" (feminine) or "m" (masculine).
ancestryNoOptional ancestry filter or custom ancestry, e.g. "Dwarven", "Elven", "Half-orc", "Halfling", "Gnomish", "Fey-touched", "Tiefling".
exportFormatNoOutput export format: "all" (default, includes both SillyTavern Character Card V2 and Foundry VTT Actor JSON), "summary", "sillytavern", or "foundry".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: zero API key, 0 credits charged, and that output includes a <=75-char greeting tuned for the free 5s talking video clip — useful downstream-coupling context. It still doesn't cover failure modes or latency.

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?

Core purpose and cost posture are front-loaded, and there is no filler or marketing fluff beyond the necessary field enumeration. The first sentence is a very dense run-on list of outputs, which is heavy but each element earns its place by telling the agent what it gets back.

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

Completeness5/5

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

With no output schema, the description takes on the job of describing the return value and does so field by field, including both export formats. All six parameters are optional and fully documented in the schema, and annotations cover safety, so nothing an agent needs to call this correctly is missing.

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 three enums and per-field examples, so the schema fully carries parameter meaning. The description adds no parameter-specific guidance beyond mentioning determinism and the export bundle generically, so the 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 ('roll') and resource ('a complete tabletop RPG / D&D NPC') and enumerates the returned bundle (name, ancestry, role, traits, quirk, plot hook, GM secret, portrait prompt, voice MP3, greeting) plus SillyTavern and Foundry exports. That level of specificity clearly separates it from siblings like create_npc_voice_line or generate_avatars, which handle single artifacts.

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?

The description implies when to use it (you want a whole NPC in one deterministic roll with VTT-ready exports), and mentions the cost/auth posture, but it never states when NOT to use it or names an alternative such as create_npc_voice_line or create_talking_video for follow-on steps. Usage is inferable rather than explicit.

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