Skip to main content
Glama

pirate-borg-mcp

An MCP server for Pirate Borg. Gives an LLM the tools it needs to generate stat-accurate NPCs using the procedural tables from the rulebook.

Tools

create_character

Generates a Pirate Borg NPC. The LLM provides narrative fields (name, faction, description, attack, inventory); the server rolls all numerical values from the enemy generator tables: HP, morale, armor tier, and the five ability score modifiers (Strength, Agility, Presence, Toughness, Spirit).

The LLM can optionally override hp_tier (1–10) or armor_tier (0–3) — useful for intentionally tough or lightly armored characters.

Returns a formatted markdown stat block.

Related MCP server: MCP Dice Roller

Setup

pnpm install
pnpm build

Connecting to Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "pirate-borg": {
      "command": "node",
      "args": ["/absolute/path/to/pirate-borg-mcp/dist/index.js"]
    }
  }
}

Development

pnpm dev   # runs src/index.ts directly with tsx (no build step)

Available Tools

1 tool
create_characterA

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.

ParametersJSON 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

TDQS

A4.3/5.0
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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedcreate_character

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no risk of ambiguity or misselection.

Naming Consistency5/5

Single tool uses clear verb_noun pattern (create_character), consistent with good naming conventions.

Tool Count4/5

A single tool is appropriate for a focused NPC generator server, though slightly thin if broader interaction is expected.

Completeness3/5

The server only supports creating characters; there are no tools for reading, updating, or deleting, which may limit agent workflows but is acceptable for a simple generator.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    A MCP server enabling LLMs to roll dice
    1
    4
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    An MCP server that provides tools for rolling dice using standard notation, flipping coins, and selecting random items from lists. It supports advanced tabletop gaming features such as character stat generation and keep-highest/lowest mechanics.
    6
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    A comprehensive MCP server for managing AI-assisted Dungeons & Dragons campaigns, featuring tools for character sheets, combat tracking, and world-building. It enables players and DMs to interact with 5e game mechanics and query personal PDF rulebooks using RAG capabilities.
    97
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables AI agents to act as dynamic dungeon masters for text-based RPGs with dynamically generated rule systems and comprehensive game state management.
    11
    10
    MIT

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