Skip to main content
Glama

simulate_attack

Predict attack outcomes without altering game state: returns expected damage, counter-damage, and death status. Optionally simulate from a different tile to evaluate move-then-attack sequences before committing.

Instructions

Read-only. Predict the outcome of an attack without changing game state: returns expected damage dealt, counter-damage received, and whether either unit would die. attacker_id and target_id are unit string identifiers from get_state. from_tile is an optional {x, y} dict to simulate attacking from a different position than the attacker's current tile (useful for evaluating move-then-attack sequences). Use this to compare attack options before committing with the attack tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes
attacker_idYes
target_idYes
from_tileNo
Behavior5/5

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

Given no annotations, the description fully discloses the read-only nature, no state change, and specifies the return format (expected damage, counter-damage, unit deaths). This exceeds expectations for a tool without annotations.

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 sentences front-load the core purpose and behavior, with no redundant information. Every sentence serves a distinct purpose: purpose, parameter details, and usage guidance.

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?

Even without an output schema, the description explains return values. It covers all parameters with relevant context, differentiates from the sibling 'attack' tool, and is self-contained for an agent to decide when to use.

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?

With 0% schema description coverage, the description adds essential meaning: it identifies 'attacker_id' and 'target_id' as unit identifiers from 'get_state', and explains 'from_tile' as an optional dict for different positions. Only 'connection_id' lacks explanation, but it is standard.

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 predicts attack outcomes without changing game state, listing specific return values. It distinguishes from the sibling 'attack' tool by explicitly stating it is read-only and used for comparison.

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 advises using this before committing with 'attack' and explains the optional 'from_tile' parameter for evaluating move-then-attack sequences. It does not explicitly state when not to use, but the context is clear.

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/haoyifan/Silicon-Pantheon'

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