Skip to main content
Glama

wound_calculator

Calculate expected wounds and damage for a Warhammer 40,000 attack sequence. Input an attack profile and target stats to get probabilities for hits, wounds, saves, and damage.

Instructions

Calculate expected wounds and damage for a Warhammer 40,000 attack sequence. Pure math — input an attack profile and target stats, get probabilities and expected results for hits, wounds, saves, and damage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attacksYesNumber of attacks
hit_skillYesBallistic Skill or Weapon Skill needed (e.g., 3 for 3+)
strengthYesWeapon strength
toughnessYesTarget toughness
armour_saveYesTarget's armour save (e.g., 3 for 3+, 7 for no save)
damageYesDamage value (e.g., '1', '2', 'D3', 'D6', 'D6+1', '2D6')
armour_penetrationNoAP value as a positive number (e.g., 2 for AP-2)
invulnerable_saveNoInvulnerable save (e.g., 4 for 4++)
feel_no_painNoFeel No Pain value (e.g., 5 for 5+++)
reroll_hitsNoRe-roll hit rolls: 'ones' = re-roll 1s, 'all' = re-roll all misses
reroll_woundsNoRe-roll wound rolls: 'ones' = re-roll 1s, 'all' = re-roll all misses
weapon_keywordsNoWeapon keywords that affect the calculation (e.g., ['Lethal Hits', 'Sustained Hits 1', 'Devastating Wounds', 'Torrent', 'Twin-linked'])
wounds_per_modelNoWounds characteristic of each target model (for models killed estimate)
game_modeNoGame mode (currently only 40k wound math is supported)40k
Behavior3/5

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

No annotations are present, so the description must cover behavior. It states 'Pure math', indicating no side effects or state changes. However, it does not disclose output format, precision, or any limitations like maximum attack count. Adequate but not thorough.

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 clearly conveying purpose and nature of the tool. No redundant or extraneous information. Front-loads the core functionality effectively.

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?

Despite 14 parameters and no output schema, the description gives a high-level overview but omits details like expected return values (probabilities, averages) or handling of multiple profiles. Could be more complete given the tool's complexity.

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 coverage is 100% with descriptive parameter definitions. The description adds no additional meaning beyond what the schema already provides. Achieves the baseline for full schema documentation.

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 calculates expected wounds and damage for a Warhammer 40k attack sequence, using specific verb 'calculate' and resource 'wounds/damage'. It explicitly says 'Pure math', distinguishing it from sibling lookup tools like lookup_unit or compare_units.

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

Usage Guidelines3/5

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

The description implies usage when an attack math calculation is needed, but does not specify when to avoid using it or mention alternatives. No explicit 'use this when' or 'do not use for' guidance is provided.

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/gregario/warhammer-oracle'

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