Skip to main content
Glama
Emieeel

Pokémon Champions MCP Server

by Emieeel

Calculate battle damage (Pokémon Champions)

calculate_damage

Calculate the damage a move deals in Pokémon Champions, factoring in abilities, items, weather, terrain, Tera, and Doubles conditions. Reports damage range, percent, and hits-to-KO.

Instructions

Calculate the damage one Pokémon deals to another with a given move in Pokémon Champions (VGC-style, defaults to Doubles). Wraps the trusted @smogon/calc engine, so abilities (Contrary, Intimidate, ...), items, weather, terrain, Tera, crits, multi-hit, screens and Doubles spread reduction are all handled correctly. For moves whose power builds up over a battle — Rage Fist (per hit taken), Last Respects (per fainted ally) — pass moveContext so the base power scales correctly; or pin any variable-power move with moveContext.basePowerOverride. Answers questions like "does my Choice Band Staraptor-Mega OHKO that Garchomp?". Returns the damage range, percent range, hits-to-KO, and the human-readable calc string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moveYesThe move the attacker uses, e.g. "Close Combat".
fieldNoBattle field/side conditions. Defaults to Doubles.
attackerYesThe attacking Pokémon and its set.
defenderYesThe defending Pokémon and its set.
moveContextNoBattle-history context for moves whose base power accumulates (Rage Fist, Last Respects), or a raw basePowerOverride for any other variable-power move.
Behavior5/5

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

No annotations are provided, so the description fully discloses behavior: it wraps the @smogon/calc engine, handles abilities/items/weather/terrain/crits/multi-hit/screens/Doubles spread, and explains moveContext for variable-power moves. It also describes the return values (damage range, percent range, hits-to-KO, calc string).

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 well-structured and front-loaded: it starts with the main purpose, then details engine capabilities, special move handling, example usage, and outputs. Each sentence contributes meaningful information without wasted words.

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?

Given the tool's complexity (nested schemas, no output schema, no annotations), the description is highly complete. It explains key mechanics, special cases, and return values, making it sufficient for an agent to select and invoke the tool correctly.

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. The description adds value by explaining the purpose of moveContext for Rage Fist/Last Respects and basePowerOverride, plus gives a concrete usage example that clarifies parameter roles.

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 damage between two Pokémon with a given move, specific to Pokémon Champions. It includes an explicit example question and distinguishes itself from sibling tools like type_effectiveness and get_pokemon by focusing on damage calculation.

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 provides clear usage context with the example 'does my Choice Band Staraptor-Mega OHKO that Garchomp?' indicating when to use the tool. It does not explicitly mention alternatives, but the context is clear without needing exclusions.

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/Emieeel/poke-mcp-tool'

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