Pokemon Go MCP Server

get_egg_recommendations

Get egg incubation recommendations tailored to your priority, such as shiny hunting, rare Pokemon, fast hatches, or specific distances.

Instructions

Get egg incubation recommendations based on specified priority.

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_egg_recommendations"
  }
}

Input Schema

Name	Required	Description	Default
`priority`	No	Priority type - "shiny" for shiny hunting, "rare" for uncommon, "quick" for fast hatches, or "distance" for specific distances	shiny

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It states the tool returns recommendations, which is likely a read-only operation, but does not explicitly confirm read-only nature, mention side effects, or disclose any constraints. The behavior is straightforward, so a 3 is appropriate.

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 sentence with no unnecessary words. It is front-loaded and concise, every part earns its place.

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 the simple input (one parameter with enum values) and the existence of an output schema, the description is mostly complete. However, it could briefly explain what 'recommendations' entails (e.g., which egg types to prioritize), but it is sufficient for a straightforward tool.

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%, and the parameter 'priority' already has a description listing the values. The tool description adds no further meaning beyond what the schema provides, so baseline 3.

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?

Description clearly states the tool returns egg incubation recommendations based on a priority. The verb 'Get' and resource 'egg incubation recommendations' are specific. It distinguishes from sibling tools like get_egg_hatches or get_shiny_egg_hatches which list hatches or shiny hatches, whereas this provides recommendations tailored to a priority.

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 when the user has a priority type (shiny, rare, quick, distance) but does not explicitly state when to use it over alternatives or when not to use it. No exclusion criteria or contextual guidance is provided.

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

Deploy Server