getcompetitive

Overview Schema Source Related Servers Discussions Admin

Check Speed against a regulation

check_speed

Read-onlyIdempotent

Compute final Speed from EVs, nature, boosts, and Choice Scarf, then compare against a Regulation roster to identify outspeed, tie, and slower matchups.

Instructions

Compute one Pokémon’s final Speed and, given a Regulation Set, rank it against that roster at its fastest (252 EV, +Spe nature) and uninvested reference speeds. Speed only: for damage use calculate_damage or calculate_matchups, and to find the Speed EVs that beat a target use optimize_evs. Applies boosts.spe (-6..+6) and Choice Scarf ×1.5; other items are reported as Speed-neutral, and regulation is optional. Returns finalSpeed, modifiers, and outspeeds/conditional/losesTo counts with up to 15 threats each. Read-only and offline; unknown names return an isError.

Input Schema

TableJSON Schema

Name	Required	Description
`evs`	No	EVs keyed by stat id; only `spe` (0-252) changes the result, e.g. { spe: 252 }.
`ivs`	No	IVs keyed by stat id; only `spe` (0-31) changes the result, and it defaults to 31.
`item`	No	Held item, e.g. "Choice Scarf"; only Choice Scarf multiplies Speed (×1.5), other items are listed as speed-neutral.
`level`	No	Level 1-100; default 50, matching VGC play.
`boosts`	No	Stat stages; only `spe` (-6..+6) is applied, e.g. { spe: 1 } for a +1 Speed stage.
`nature`	No	Nature name, e.g. "Jolly", "Timid"; default Serious (neutral Speed).
`species`	Yes	Species or form name, e.g. "Dragapult", "Ogerpon-Wellspring".
`regulation`	No	Regulation Set name or id from `list_regulations` to compare against, e.g. "Regulation Set G"; omit to get the raw Speed only.
`championsPoints`	No	The same Speed investment in Pokémon Champions stat points, e.g. { spe: 32 } for a maxed Speed stat; give this or `evs`, not both.

Output Schema

TableJSON Schema

Name	Required	Description
`evSpe`	Yes	Speed EVs invested, 0-252.
`ivSpe`	Yes	Speed IV used, 0-31.
`level`	Yes	Level the Speed was computed at, 1-100.
`nature`	Yes	Nature applied Speed, e.g. "Jolly" for +Spe; Serious when the call omitted one.
`baseSpe`	Yes	The species’ base Speed stat, before level, IVs, EVs, nature, item, and boosts.
`species`	Yes	Canonical species name the Speed belongs to, e.g. "Dragapult".
`modifiers`	Yes	Human-readable list of everything that changed the Speed stat, e.g. ["Speed stage +1", "Choice Scarf x1.5"]; a speed-neutral item is noted here too, and the list is empty when nothing applied.
`comparison`	No	Present only when `regulation` was supplied: how this Speed places against that roster, whose threat lists are each capped at 15 entries.
`finalSpeed`	Yes	The final Speed stat after level, IVs, EVs, nature, Speed stage, and item; this is the number turn order compares.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.2.0Sep 18, 2026

removedInput schema / properties / generation

Removed value: -{
-  "default": 9,
-  "description": "Generation whose data to use, 1-9 (default 9). Earlier generations omit moves, items, abilities, and forms that did not exist yet.",
-  "maximum": 9,
-  "minimum": 1,
-  "type": "integer"
-}

removedOutput schema / properties / generation

Removed value: -{
-  "description": "Generation whose base stats and mechanics were used, 1-9.",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

changedOutput schema / required

Previous value: -[
-  "species",
-  "generation",
-  "level",
-  "nature",
-  "baseSpe",
-  "evSpe",
-  "ivSpe",
-  "finalSpeed",
-  "modifiers"
-]New value: +[
+  "species",
+  "level",
+  "nature",
+  "baseSpe",
+  "evSpe",
+  "ivSpe",
+  "finalSpeed",
+  "modifiers"
+]

Changed1 schema field changedv2.0.2Sep 18, 2026

addedInput schema / properties / championsPoints

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "description": "The same Speed investment in Pokémon Champions stat points, e.g. { spe: 32 } for a maxed Speed stat; give this or `evs`, not both.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Addedv2.0.0Sep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses key calculation behaviors: it applies only `boosts.spe` (-6..+6) and Choice Scarf ×1.5, treats other items as Speed-neutral, and returns an `isError` for unknown names. It summarizes the return shape (finalSpeed, modifiers, outspeeds/conditional/losesTo counts) without contradicting any annotation.

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 compact and front-loaded: the main purpose is stated in the first sentence, followed by explicit alternatives, calculation rules, and return summary. Each sentence adds distinct, necessary information with no redundancy or filler.

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 (9 params, nested objects) and the rich output schema, the description is complete. It covers scope, optionality, error behavior, and decision routing to siblings, leaving no critical ambiguity for an agent to call and interpret the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description repeats what the schema already states: only `spe` EV/IV/boosts affect the result, only Choice Scarf modifies Speed, and `regulation` is optional. It adds no new parameter meaning beyond a concise summary, so it does not exceed the baseline.

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 opens with a specific verb-resource pair: 'Compute one Pokémon’s final Speed and, given a Regulation Set, rank it against that roster.' It also explicitly differentiates from siblings by stating 'Speed only: for damage use `calculate_damage` or `calculate_matchups`' and points to `optimize_evs` for EV tuning, making the tool's unique role unmistakable.

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

Usage Guidelines5/5

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

The description gives concrete when-to-use guidance ('Speed only', 'given a Regulation Set', 'regulation is optional') and explicit when-not-to-use guidance with named alternatives for damage and EV optimization. It also notes the tool is read-only and offline, which helps an agent decide when it is safe to invoke.

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