VGC Teambuilder

Compare Speed and turn order

compare_speed

Read-onlyIdempotent

Work out the Speed of several Pokémon in Pokémon Champions and the order they move in, including the effect of items such as Choice Scarf, Tailwind, paralysis, stat stages, weather abilities and Trick Room. Use it to answer who outspeeds whom. Any part of a set that is left out is filled in from the regulation's usage statistics and listed under assumptions. Speed decides order only among moves of the same priority.

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": {
      "pokemon": "<pokemon>"
    },
    "name": "compare_speed"
  }
}

Input Schema

Name	Required	Description
`format`	No	Regulation id from list_formats. Defaults to "champions-regmc" (Pokémon Champions — Regulation M-C).
`pokemon`	Yes	The Pokémon to compare. The same Pokémon may appear with two sets.
`terrain`	No
`weather`	No
`trickRoom`	No	Trick Room is up: slower moves first

Output Schema

Name	Required	Description
`ties`	Yes	Groups with equal Speed
`order`	Yes	First to move first
`format`	Yes	Regulation id the result applies to
`trickRoom`	Yes
`conditions`	Yes
`formatName`	Yes	Display name of the regulation
`assumptions`	Yes	Everything the calculation assumed, including any part of a set that was filled in because it was not given. Tell the user about these.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the remaining burden is low. The description still adds genuinely useful behavior: omitted set details are silently filled from the regulation's usage statistics and surfaced under `assumptions`, and Speed only decides order within the same priority bracket. Those are non-obvious traits an agent would otherwise get wrong.

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?

Four short sentences: purpose first, then the use case, then the defaulting behavior, then the priority caveat. Nothing is padding and the most decision-relevant facts are front-loaded.

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?

An output schema exists, so return shape need not be explained, and annotations cover the safety profile. What remains — what the tool computes, how missing inputs are resolved, and the priority caveat — is all present, which is sufficient for a read-only calculation tool with five parameters.

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 coverage is 60%, and the description mostly restates what the schema already documents (items, Tailwind, paralysis, stat stages, Trick Room). Parameters with no schema description, notably `weather` and `terrain`, get no explanation in the description either, so the coverage gap is not compensated. Baseline 3 is appropriate.

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 names a specific verb and resource: working out Speed values and the resulting move order for several Pokémon, plus the modifiers that feed into it (Choice Scarf, Tailwind, paralysis, stat stages, weather abilities, Trick Room). It is clearly distinguishable from siblings like calculate_damage or analyze_team_types, which deal with damage or team composition rather than turn order.

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?

"Use it to answer who outspeeds whom" gives a concrete trigger for calling the tool, and the closing note about priority scopes when the answer applies. There is no explicit when-not guidance or named alternative (e.g. calculate_damage for damage questions), so it stops short of full routing guidance.

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

All VGC Teambuilder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.