VGC Teambuilder

Check which moves a Pokémon can learn

validate_moveset

Read-onlyIdempotent

Check whether a Pokémon can learn each of the given moves in any Pokémon game, counting moves inherited from its pre-evolutions and base form. Based on Pokémon Showdown learnset data across all generations, not Pokémon Champions' own move lists: a move learnable only in an older game may not exist in Champions, and a move added only in Champions may be reported as not learnable.

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>",
      "moves": "<moves>"
    },
    "name": "validate_moveset"
  }
}

Input Schema

Name	Required	Description	Default
`moves`	Yes	Move names to check
`pokemon`	Yes	Pokémon name in English, e.g. "Incineroar" or "Landorus-Therian"

Output Schema

Name	Required	Description	Default
`moves`	Yes
`pokemon`	Yes
`allLearnable`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior: results derive from Showdown learnsets rather than Champions' own lists, so older-game-only moves may be false positives and Champions-only moves may be reported as unlearnable.

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?

Two sentences, front-loaded with the core action, followed by the one caveat an agent must know. No filler or repetition of the title.

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?

With an output schema present, return values need not be explained, and the description covers the key semantic caveats (cross-generation data, inheritance). Only minor gap is the absence of any note on how partial results or invalid names are handled.

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 100% and both parameters are documented in the schema, including the English-name example. The description adds only the semantic that inheritance from pre-evolutions is considered, not per-parameter detail, so the baseline 3 applies.

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 specific verb ('check whether') and resource ('moves a Pokémon can learn'), and scopes it precisely: per-move, across any game, including moves inherited from pre-evolutions and base form. That scope distinguishes it from team-level siblings like validate_team without needing to name them.

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

Usage Guidelines3/5

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

Usage is implied by the purpose (verify learnability of a set of moves) but there is no explicit when-to-use/when-not guidance and no named alternative. The data-source caveat is helpful context but is not 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.