Skip to main content
Glama

wound_calculator

Compute expected wounds and damage for Warhammer 40,000 attacks. Input attack profile and target stats to obtain 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 provided, so the description carries the full burden. It states 'Pure math' indicating no side effects, but does not disclose other behaviors like deterministic output, statelessness, or rate limits. The description is adequate but minimal, missing explicit assurance that the tool is safe and non-destructive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loading the purpose. It is concise and free of unnecessary words. However, it could be slightly more structured to separate purpose from constraints (like the game_mode limitation, which is only in parameter descriptions). Overall efficient.

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?

With 14 parameters, no output schema, and no annotations, the description is somewhat incomplete. It explains what the tool does but does not describe the output format (e.g., probabilities, expected values, distribution). For a calculator tool, the agent would benefit from knowing what the returned data looks like. The description suffices for basic understanding but lacks completeness for seamless integration.

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?

Input schema has 100% description coverage, so the schema already documents parameters well. The tool description adds minimal extra meaning, mainly stating 'game_mode (currently only 40k wound math is supported)' which clarifies a constraint. This meets the baseline but does not substantially enhance understanding beyond 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 the tool's function: 'Calculate expected wounds and damage for a Warhammer 40,000 attack sequence.' It uses a specific verb (calculate) and resource (attack sequence), and distinguishes from sibling tools like compare_units or lookup_* by focusing on probability and expected results.

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 implies usage for pure math calculations, but does not explicitly state when not to use it or suggest alternatives. It mentions 'Pure math' and input/output, which gives context but lacks exclusionary guidance. Given clear sibling tools, the context is sufficient for an agent to infer appropriate usage.

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