Skip to main content
Glama

create_character

Create a Pirate Borg NPC with procedurally rolled stats from enemy generator tables. Provide narrative details; the tool rolls all numerical values like HP, morale, armor, and ability modifiers.

Instructions

Generate a Pirate Borg NPC with procedurally rolled stats (HP, morale, armor, ability modifiers). You supply the narrative fields; the tool rolls all numerical values from the enemy generator tables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe character's name
factionYesThe faction this character belongs to
hp_tierNoHP tier 1–10 from the enemy generator table. If omitted, rolled with d10.
summaryYesA brief one-sentence description of the character
inventoryNoList of items the character carries
armor_tierNoArmor tier 0–3 from the enemy generator table. If omitted, rolled with d4.
attack_nameYesName of the primary attack (e.g. 'Cutlass', 'Flintlock Shot')
descriptionYesLonger narrative description: appearance, personality, mannerisms, role in the world
attack_descriptionYesFull attack description including narrative flavour and any special effects or conditions
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that stats are procedurally rolled from tables, which informs the agent of random outcomes. It does not mention any destructive side effects, but as a creation tool, that is expected.

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?

Two sentences, no wasted words. The description is front-loaded with the core action and immediately clarifies the user-tool responsibility split.

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

Completeness3/5

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

The description lacks information about the return format (what the output object looks like) and does not mention that ability modifiers are not in the schema. Given no output schema, this gap leaves the agent uncertain about what the tool returns.

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 coverage is 100%, so baseline is 3. The description adds value by grouping parameters into 'narrative fields' vs 'rolled numerical values', helping the agent understand the division of labor beyond individual schema descriptions.

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 uses a specific verb ('Generate') and resource ('Pirate Borg NPC'), and clearly distinguishes the tool's role: user supplies narrative fields, tool rolls stats from tables. This leaves no ambiguity about what the tool does.

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

Usage Guidelines4/5

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

The description tells the agent when to use this tool: when creating an NPC and wanting randomly generated stats. It does not explicitly state when not to use it or list alternatives, but since no sibling tools are provided, this is sufficient context.

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/samhooker/pirate-borg-mcp'

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