Skip to main content
Glama

pokemon

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Ability

get_ability
Read-onlyIdempotent

Look up a Pokémon ability (e.g., "static", "overgrow"). Returns effect description and all Pokémon that can have this ability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
abilityYesAbility name (e.g., "overgrow", "blaze", "static")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAbility name
effectYesFull English effect description
pokemonYesPokémon that can have this ability
short_effectYesShort English effect description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "effect": {
+      "description": "Full English effect description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Ability name",
+      "type": "string"
+    },
+    "pokemon": {
+      "description": "Pokémon that can have this ability",
+      "items": {
+        "properties": {
+          "is_hidden": {
+            "description": "Whether this is a hidden ability for this Pokémon",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Pokémon name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "is_hidden"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "short_effect": {
+      "description": "Short English effect description",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "name",
+    "effect",
+    "short_effect",
+    "pokemon"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ability": "static"
+  },
+  {
+    "ability": "overgrow"
+  }
+]
  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 the tool read-only, idempotent, and non-destructive. The description adds value by specifying the output content ('effect description and all Pokémon that can have this ability') and giving concrete examples. No contradictions with annotations. The description provides useful behavioral detail beyond the structured metadata.

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 one sentence, front-loaded with the action and resource, and includes examples plus return summary. Every word is informative; there is no redundant or extraneous content.

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?

This is a simple tool with one parameter, full schema coverage, rich annotations, and an existing output schema. The description fully covers the purpose and return behavior, making it complete for an agent to select and invoke correctly.

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% for the single 'ability' parameter, with the schema already including a description and examples. The tool description repeats the examples but adds no new semantic information beyond what the schema provides. 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 the tool's function: 'Look up a Pokémon ability' with examples ('static', 'overgrow') and specifies the return value ('effect description and all Pokémon that can have this ability'). It clearly distinguishes itself from sibling tools like get_pokemon and get_type by focusing specifically on abilities.

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?

The description provides clear context that this tool is for looking up Pokémon abilities, which implies when to use it. However, it does not mention alternatives or explicitly state when not to use it. Thus it meets the 'clear context, no exclusions' level.

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