Skip to main content
Glama

poke_get_generation

Read-onlyIdempotent

Retrieves Pokémon generation details, including region and species list, by generation ID or name to support Pokédex lookups and game data workflows.

Instructions

Get Pokemon generation info, region, and species list.

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": {
      "generation": "<generation>"
    },
    "name": "poke_get_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
generationYesGeneration ID (1-9) or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description. The description adds the useful detail that results include region and species list, but says nothing about invalid generation IDs, error behavior, or result size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the returned fields are enumerated rather than left vague. It is efficient, though almost minimal for a schema-bearing tool.

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?

For a simple one-parameter read tool with full annotation coverage and no output schema, the description tells the agent what it returns (info, region, species list), which is the main missing structured detail. Only error and edge-case behavior is left unaddressed.

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%; the schema states the parameter is a generation ID (1-9) or name. The description adds no further semantics such as accepted name formats or case handling, so the baseline 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 gives a specific verb ('Get') and a distinct resource ('Pokemon generation'), and even names the payload (region and species list). The generation resource is clearly separate from sibling resources like pokemon, type, and ability, though the description never explicitly contrasts 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 only implied: an agent infers this is the lookup for a generation index or name. There is no statement of when to prefer it over poke_get_pokemon or the other PokeAPI siblings, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools