Skip to main content
Glama

pokemon

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Evolution Chain

get_evolution_chain
Read-onlyIdempotent

Trace a full evolution line by chain ID. Returns each stage with evolution triggers, level requirements, and items needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEvolution chain ID (e.g., 1 for Bulbasaur line, 10 for Caterpie line)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEvolution chain ID
chainYesFlattened evolution chain entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chain": {
+      "description": "Flattened evolution chain entries",
+      "items": {
+        "properties": {
+          "evolution_trigger": {
+            "description": "Evolution trigger name (e.g., level-up, item)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "item": {
+            "description": "Item name required for evolution",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "min_level": {
+            "description": "Minimum level for evolution",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "species": {
+            "description": "Species name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "species",
+          "evolution_trigger",
+          "min_level",
+          "item"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Evolution chain ID",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "chain"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1
+  },
+  {
+    "id": 10
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description doesn't need to cover safety. It adds value by disclosing the return payload details (stages, triggers, levels, items), which are beyond the annotations. No contradictions exist.

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?

The description is a single, compact sentence that front-loads the action ('Trace a full evolution line') and then lists key return elements. Every clause earns its place with no wasted words.

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?

With an output schema present and annotations covering safety, the description fully specifies what the tool does and what it returns. The simple one-parameter interface and straightforward purpose mean no additional context is necessary.

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?

The schema description for 'id' provides full coverage (100%) with examples (1 for Bulbasaur, 10 for Caterpie). The tool description's mention of 'chain ID' is redundant with the schema, adding no new parameter semantics. Baseline of 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 clearly states a specific verb ('trace'), a resource ('full evolution line'), and the lookup method ('by chain ID'), distinguishing it from sibling tools like get_pokemon or get_type. The mention of returning stages with triggers, level requirements, and items leaves no ambiguity about its function.

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?

While it doesn't explicitly name alternative tools or exclusion conditions, the description strongly implies use when needing an evolution chain by ID. The context is clear and distinct from siblings, but lacks explicit when-not or alternative guidance, keeping it a step below the highest bar.

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

All pokemon toolsInspect
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.

Resources