Skip to main content
Glama
Niclasp1501

ninjos-foundry-mcp

by Niclasp1501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a DSA5 character from an archetype

create-dsa5-character-from-archetype

Create a DSA5 hero by copying an archetype, set a unique name and optional details, then add the actor to the Foundry VTT world or prepare it without saving.

Instructions

[DSA5 only] Create one hero as a copy of an archetype from list-dsa5-archetypes, with a new name and optional details (age, biography, gender, eye and hair color, height, weight, species, culture, profession) written onto the hero and read back. The hero goes into the folder "Foundry MCP Actors", without a token in a scene, linked to its archetype. A name another actor has already (ignoring case) is refused. addToWorld false only prepares the hero and shows it, without writing anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addToWorldNofalse only prepares the hero and shows it, without writing anything
archetypeIdYesId of the archetype inside that compendium
characterNameYesName of the new hero; a name another actor has (ignoring case) is refused
customizationNoDetails written onto the hero and read back
archetypePackIdYesId of the compendium that holds the archetype, as list-dsa5-archetypes shows it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv14.2609.4

TDQS

A4.4/5.0
Behavior5/5

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

The description richly discloses side effects and behaviors beyond the sparse annotations: the hero lands in 'Foundry MCP Actors', has no token in a scene, remains linked to its archetype, duplicate names are refused, and addToWorld false prevents any write. This far exceeds the annotation's minimal safety hints.

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?

Three dense sentences deliver scope, destination, linking behavior, duplicate handling, and the dry-run flag with no filler. The most important constraints are front-loaded, and every clause earns its place.

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?

For a tool with a nested customization object and no output schema, the description covers the critical context: source, destination, write behavior, uniqueness rule, and no-token outcome. The only small gap is not specifying the exact return shape, though 'read back' hints at the response.

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%, so the schema already documents every parameter. The description adds a useful pointer that archetypePackId is shown by list-dsa5-archetypes and restates the addToWorld behavior, but most parameter-level meaning is already present in the schema.

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 a specific verb and resource: 'Create one hero as a copy of an archetype', and identifies the source explicitly via 'list-dsa5-archetypes'. It also distinguishes itself from the related read-only sibling by describing the actual creation behavior, making the tool's role unambiguous.

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 '[DSA5 only]' prefix gives a clear system-scoping condition, and the reference to list-dsa5-archetypes as the required source indicates when this tool is appropriate. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to select it correctly.

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

Deploy Server

Other Tools