Skip to main content
Glama
Sign In
PokeMCP

PokeMCP

by adamescj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wait_frames

Pauses gameplay for a specified number of frames and captures a screenshot, useful for waiting through animations, text, or transitions in Pokemon Fire Red.

Instructions

Wait for a number of frames without input, then screenshot.

Useful for waiting through animations, text, or transitions. At ~60fps, count=60 is approximately 1 second.

Args: count: Number of frames to wait (default 60)

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": "wait_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: waiting without input, then automatically taking a screenshot. It includes performance context (frame rate approximation) but doesn't specify error handling or output format details.

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 perfectly structured and concise: a clear purpose statement, usage guidelines, timing context, and parameter explanation in just four sentences. Every sentence adds value with zero redundancy or wasted words.

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?

For a single-parameter tool with no annotations or output schema, the description provides excellent coverage of purpose, usage, and parameter semantics. The only minor gap is not explicitly describing the screenshot output format, but given the tool's simplicity and clear sibling context, this is a minor omission.

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

Parameters5/5

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

The schema has 0% description coverage, so the description must fully compensate. It provides clear semantics for the single parameter: explains what 'count' represents (number of frames to wait), provides a default value (60), and adds crucial context about timing conversion (frames to seconds). This goes well beyond what the bare schema provides.

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 purpose with specific verbs ('wait for a number of frames', 'screenshot') and distinguishes it from siblings like get_screenshot (which only captures) or press_button (which interacts). It explicitly identifies the resource (frames) and outcome (screenshot).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('waiting through animations, text, or transitions') and includes a practical timing reference ('~60fps, count=60 is approximately 1 second') that helps differentiate it from time-based waiting alternatives not present in the sibling list.

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