Skip to main content
Glama

Compare enhancements against a unit

compare_enhancements
Read-onlyIdempotent

Simulates the attacking unit once with each enhancement its characters, including attached leaders, can take in the attacker's detachment, and once with none, against the defender, as simulate_combat does. Takes the same sides as simulate_combat; name the attacker's detachment, since enhancements come from it. Any enhancement the sides name is replaced by the one being compared. points keeps only enhancements costing that much or less, such as the points a list has spare. mode ranks shooting followed by melee (combined), or one phase. Returns without, the result with no enhancement, and enhancements, best first, each with its bearer, points and outcome. An enhancement with notCalculated has rules the simulator cannot estimate, so its outcome leaves them out; say so rather than ranking it. It compares damage against this one defender only, never what an enhancement does for movement, durability elsewhere or scoring.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "attacker": "<attacker>",
      "defender": "<defender>"
    },
    "name": "compare_enhancements"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoWhat to rank by: shooting followed by melee (combined), shooting alone (ranged), or melee alone.combined
pointsNoOnly enhancements costing at most this many points, such as the points the list has left.
attackerYes
defenderYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
modifiersNoSituational modifiers the simulator page offers, such as { "all": { "cover": true, "hitModifier": -1 } }, { "melee": { "charged": true } }, or { "target": { "invulnerable": 4 } }. commandReroll spends one Command Re-roll per phase on the first failed hit, wound, or save roll, or the first single-die Attacks roll below its average; compare with a run without it to judge the CP.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, non-destructive call, so the description focuses on what the annotations cannot: the return shape (baseline 'without', then 'enhancements' best-first with bearer/points/outcome), the notCalculated caveat that outcomes omit unmodelled rules and must not be ranked, and the replacement rule for any enhancement the sides already name.

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?

Front-loaded with what the tool does and how it differs from simulate_combat, and every subsequent sentence adds a distinct operational fact. Some sentences are long and chain multiple clauses (the 'Returns...' and 'notCalculated' sentences), but none are filler.

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 high-complexity, seven-parameter tool with no output schema, it covers the essentials: return ordering and fields, the detachment prerequisite, and the analytical blind spots. Minor gaps remain, such as failure modes when no enhancements qualify under points or when the detachment has none, but nothing critical is missing.

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 71%, so the schema carries most of the burden, but the description adds real meaning beyond it: points is a ceiling on enhancement cost tied to spare list points, mode ranks combined (shooting then melee) or a single phase, and the enhancement fields are replaced by the compared one rather than added.

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?

States a precise verb and resource: it simulates the attacker once per enhancement its characters (including attached leaders) can take in the attacker's detachment, and once with none. That baseline-comparison framing plus the explicit 'as simulate_combat does' makes it immediately distinguishable from the plain simulator sibling.

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?

Gives clear operating context: it takes the same sides as simulate_combat, requires the attacker's detachment to be named since enhancements come from it, and points filters candidates by spare list points. It also states a hard scope limit (damage against this one defender, not movement/durability/scoring), though it never explicitly says when to use simulate_combat instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources