Skip to main content
Glama
Sign In
PokeMCP

PokeMCP

by adamescj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_game_state

Retrieve real-time Pokemon game data including player location, badges, party Pokemon details, and battle status from RAM.

Instructions

Read the full game state from RAM.

Returns a summary of: player location, badges, money, party Pokemon (species, level, HP, moves), and whether a battle is active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool reads from RAM and returns a summary of specific game aspects, which helps understand its read-only nature and output format. However, it lacks details on potential side effects, error conditions, or performance characteristics like latency or rate limits.

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 front-loaded with the core purpose in the first sentence, followed by a concise list of returned data. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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 tool's simplicity (0 parameters, no annotations, but with an output schema), the description is mostly complete. It explains what the tool does and what it returns, which is sufficient for a read operation. However, it could benefit from more behavioral context, such as any limitations or dependencies, to fully compensate for the lack of annotations.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and output. This meets the baseline for tools with no parameters.

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 explicitly states the action ('Read the full game state from RAM') and specifies the resource ('game state'), distinguishing it from siblings like get_battle_state or get_party by covering a broader scope. It clearly articulates what the tool does without being tautological.

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 implies usage context by detailing what information is returned (e.g., player location, badges, party Pokemon), suggesting it should be used when a comprehensive game state overview is needed. However, it does not explicitly state when to use this tool versus alternatives like get_battle_state or get_party, nor does it provide 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