Skip to main content
Glama

VGC Teambuilder

Look up a Pokémon

lookup_pokemon
Read-onlyIdempotent

Get a Pokémon's types, base stats, abilities, weight, alternate forms and any Mega Evolutions legal in the supported regulations (with the Mega's types, ability and base stats). Data comes from Pokémon Showdown; it does not say whether the Pokémon itself is legal in a format — use validate_team for that.

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

Input Schema

NameRequiredDescriptionDefault
pokemonYesPokémon name in English, e.g. "Incineroar" or "Landorus-Therian"

Output Schema

NameRequiredDescriptionDefault
nameYes
typesYes
weightKgNo
abilitiesYes
baseStatsYes
dexNumberYes
otherFormsYes
baseSpeciesNoSet when this is an alternate form
megaEvolutionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description focuses on what annotations cannot say: the data source is Pokémon Showdown and the Mega-form data is scoped to supported regulations. That regulatory scoping caveat is genuinely useful context beyond structured fields.

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 returned data and closed with the sharpest boundary (legality). No filler, no repetition of the title.

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?

For a single-parameter read tool with an output schema and full annotations, nothing an agent needs to call it correctly is missing; the source and regulatory caveats are exactly the residual gaps the structured fields cannot fill.

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% and the single parameter is fully documented with name format examples in the schema itself. The description adds nothing about the input, 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 and resource and then enumerates exactly what comes back (types, base stats, abilities, weight, alternate forms, legal Megas with their own types/ability/stats). It also explicitly differentiates itself from validate_team, so an agent can separate it from the legality sibling without opening either schema.

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?

Gives a concrete exclusion and a named alternative: the tool does not report whether the Pokémon itself is legal, and validate_team is the tool for that. It does not address the other adjacent siblings (e.g. get_pokemon_usage, get_checks_and_counters), but the primary misuse case is clearly closed off.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.