Skip to main content
Glama
Sign In
Pokemon Go MCP Server

Pokemon Go MCP Server

by GhostTypes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_rocket_encounters

Retrieve all possible Pokemon encounter rewards from Team Rocket trainer battles, organized by trainer type.

Instructions

Get all possible Team Rocket encounter rewards.

Returns information about Pokemon you can catch after defeating Team Rocket trainers, organized by trainer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rocket_encounters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'returns information' implying a read operation, but does not explicitly confirm no side effects, authentication needs, or rate limits. Additional behavioral details are absent.

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 concise (two sentences, 20 words) and front-loaded with the main action. Every word is meaningful with no redundancy.

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?

Given that an output schema exists and there are no parameters, the description sufficiently states what the tool returns and how it is organized. It covers the key purpose, though it could mention the output format briefly if the schema is not self-explanatory.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the schema coverage is 100%. According to guidelines, zero parameters gives a baseline of 4, and the description does not need to add parameter semantics.

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 retrieves all possible Team Rocket encounter rewards, organized by trainer. The verb 'get' and resource 'encounter rewards' are specific and distinguishable from sibling tools like get_rocket_trainer_details or get_team_rocket_lineups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as get_rocket_trainer_details or get_team_rocket_lineups. It only states what it does without specifying context or exclusions.

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