Skip to main content
Glama

Update a WFRP4e stat block

wfrp4e-update-actor
Idempotent

Update an existing WFRP4e actor's characteristics, wounds, skills, career, movement, or biography. Changes are applied, recomputed, and reported with old and new values.

Instructions

[WFRP4e only] Change the stat block of an existing wfrp4e actor: initial, advances and modifier of characteristics, current and maximum wounds, advances of skills the actor already has, which career is current, movement and biography. Only given fields change; value, bonus and skill totals are recomputed by wfrp4e. Skills and careers match by name ignoring case; one that is missing or there twice is skipped and named in warnings, never guessed. Every value is read back; the answer lists old and new values, the new characteristic totals and anything stored differently. New skills, talents, trappings or careers: wfrp4e-add-items. A new actor: create-actor-from-compendium.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorYesId or exact name of the actor (a token id works too)
careerNoName of a career item on the actor that becomes the current one; every other career stops being current.
skillsNoAdvances for skills the actor has already; new skills come with wfrp4e-add-items.
woundsNoCurrent and maximum wounds.
movementNoMovement value (system.details.move.value).
biographyNoNew biography, replacing the old one; HTML is allowed.
characteristicsNoChanges per characteristic, keys ws, bs, s, t, i, ag, dex, int, wp, fel; each sets initial, advances and/or modifier. Value and bonus follow by themselves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv14.2609.4

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (idempotent, non-destructive, non-read-only), the description discloses meaningful runtime behavior: value/bonus/skill totals are recomputed, duplicate or missing skills/careers are skipped and reported in warnings rather than guessed, and every value is read back and echoed as old/new values. No contradiction with annotations exists.

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 dense but well-organized: purpose first, then behavioral guarantees, then explicit alternatives. Every sentence adds necessary information, and there is no filler or repetition of the schema.

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?

For a mutation tool with no output schema, the description adequately covers what the agent needs: what can be changed, how matching works, what is recomputed, what the response will contain, and which sibling tools cover adjacent operations. It is complete for correct invocation.

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 100%, so the baseline is 3, but the description adds real semantic value: it explains that characteristic totals follow automatically, that skills advances apply only to already-owned skills, that careers are matched by name, and that biography replaces the old one. These details go beyond the bare 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 and resource: 'Change the stat block of an existing wfrp4e actor' and enumerates exactly which fields are affected. It also distinguishes itself from sibling tools by naming wfrp4e-add-items and create-actor-from-compendium for adjacent use cases.

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 explicitly states what this tool is for and gives clear routing guidance: use wfrp4e-add-items for new skills/talents/trappings/careers and create-actor-from-compendium for a new actor. It also clarifies that only given fields change and that matches are by name ignoring case, so an agent knows when this tool applies.

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