Skip to main content
Glama
Sign In
Pokemon Go MCP Server

Pokemon Go MCP Server

by GhostTypes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_raid_boss

Check if a specific Pokemon is currently available in raids by entering its name.

Instructions

Search for a specific Pokemon in current raids.

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_name": "<pokemon_name>"
    },
    "name": "search_raid_boss"
  }
}

Input Schema

NameRequiredDescriptionDefault
pokemon_nameYesName of the Pokemon to search for

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. The description fails to disclose behavioral traits such as what happens if the Pokemon is not found, rate limits, or response format beyond the basic action.

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?

Single sentence description is efficient but lacks structural elements like bullet points or examples. It earns its place but could be more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists (unseen), the description is adequate for a simple search tool. However, it lacks context about valid name inputs or scenario usage, making it minimally complete.

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 coverage is 100% with a clear schema description for 'pokemon_name'. The tool description adds no extra semantic value beyond the schema, so baseline 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 verb ('Search') and resource ('specific Pokemon in current raids'), distinguishing it from siblings like 'search_pokemon_everywhere' which searches all contexts.

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 description implies usage for checking a Pokemon's presence in current raids but does not explicitly state when to use it over alternatives like 'get_current_raids' or 'search_pokemon_everywhere'.

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