Skip to main content
Glama

spawn_equipped_character

Create RPG characters with pre-equipped gear in one API call to reduce multiple operations into a single efficient request.

Instructions

Create a character with equipment from presets in a single call.

REPLACES: create_character + N×(create_item + give_item + equip_item) (8-16 calls → 1 call) TOKEN SAVINGS: ~85%

Equipment can be preset names or full item specs.

Example - Dwarf Fighter: { "name": "Gimli", "race": "Dwarf", "characterClass": "fighter", "level": 5, "stats": { "str": 18, "dex": 12, "con": 16, "int": 10, "wis": 12, "cha": 8 }, "equipment": ["battleaxe", "chain_mail", "shield"], "partyId": "fellowship-123" }

Example - From creature template: { "template": "bandit_captain", "name": "Red Raven", "equipment": ["rapier", "studded_leather"], "characterType": "npc" }

Available equipment presets: All PHB weapons (longsword, shortbow, greataxe...), armor (chain_mail, plate, leather...), and gear (rope, torch, healers_kit...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNoCreature template to use as base stats
nameYesCharacter name
raceNoHuman
characterClassNofighter
levelNo
statsNo
hpNo
maxHpNo
acNo
equipmentNoEquipment presets to create and equip
characterTypeNopc
partyIdNoParty to add character to
partyRoleNomember
sessionIdNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it creates a character with equipment in one call, supports preset names or full item specs, and includes examples showing input structure. However, it lacks details on error handling, permissions, or rate limits, which would be useful for a mutation tool.

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 well-structured and front-loaded: it starts with the core purpose, followed by replacement context, token savings, parameter details, and examples. Every sentence adds value, with no wasted words, making it efficient for an AI agent to parse.

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?

Given the tool's complexity (14 parameters, no output schema, no annotations), the description does a good job of covering essentials: purpose, usage, parameters, and examples. It addresses the mutation nature and equipment handling. However, it could improve by mentioning output format or error cases, which would help for a tool with many inputs and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (29%), but the description compensates by explaining key parameters: it clarifies that 'equipment' can be 'preset names or full item specs', lists available presets (e.g., 'PHB weapons, armor, gear'), and provides examples that illustrate usage of 'template', 'name', 'stats', etc. This adds significant meaning beyond the schema, though some parameters (e.g., 'sessionId') remain less explained.

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?

The description clearly states the tool's purpose: 'Create a character with equipment from presets in a single call.' It specifies the verb ('Create'), resource ('character'), and scope ('with equipment from presets'), and distinguishes it from sibling tools by explicitly mentioning it replaces 'create_character + N×(create_item + give_item + equip_item)'.

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?

The description provides explicit usage guidance: it states when to use this tool ('REPLACES: create_character + N×(create_item + give_item + equip_item)') and includes practical examples (e.g., 'Dwarf Fighter', 'From creature template') that illustrate common scenarios. It also mentions token savings (~85%), which helps prioritize this tool over alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/rpg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server