VGC Teambuilder

Get how a Pokémon is built

get_pokemon_usage

Read-onlyIdempotent

Show how one Pokémon is typically built in a regulation: its usage and rank, and the most common abilities, items, moves and stat spreads as a share of its recorded sets. Spreads use the stat-point scale the ladder records (0–32 per stat in Pokémon Champions).

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": "get_pokemon_usage"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	Regulation id from list_formats. Defaults to "champions-regmc" (Pokémon Champions — Regulation M-C).
`pokemon`	Yes	Pokémon name in English. Mega Evolutions are tracked separately, e.g. "Charizard-Mega-Y"

Output Schema

Name	Required	Description
`rank`	Yes
`items`	Yes
`moves`	Yes
`format`	Yes	Regulation id the result applies to
`pokemon`	Yes
`spreads`	Yes
`abilities`	Yes
`formatName`	Yes	Display name of the regulation
`usagePercent`	Yes	Share of teams, 0–100

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real behavioral context the annotations don't: results are shares of recorded sets, and spreads are expressed on the ladder's 0–32 stat-point scale in Pokémon Champions — a domain caveat that prevents misreading the numbers.

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 purpose and followed by the one interpretive detail that matters. No filler, no restatement of the title or name, and the scale caveat is placed where it will be read before interpreting output.

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, the description needn't enumerate return fields, yet it does so at a useful level, and annotations handle the safety profile. The remaining gap is routing guidance against the many usage-oriented siblings, which would complete an otherwise solid definition.

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%, with both the format enum (including its default) and the Pokémon name (including Mega Evolution naming) documented in the schema. The description adds only the loose notion of 'a regulation' and does not clarify format selection or naming beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Show how one Pokémon is typically built in a regulation') and enumerates the returned facets: usage, rank, common abilities, items, moves and stat spreads. An agent can tell this is a single-Pokémon profile rather than a list or trend tool, though no sibling is named explicitly.

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?

The phrase 'one Pokémon ... in a regulation' implies the single-entity lookup case and the need to supply a format, but there is no explicit when-to-use or when-not-to-use guidance relative to get_top_usage, get_usage_trend, or lookup_pokemon. The distinction from those siblings is left to inference.

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.