Skip to main content
Glama
Sign In
Godot MCP

Godot MCP

by KeeVeeG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

replay_gameplay

Replay a recorded gameplay session at adjustable speed for review or analysis of past playthroughs.

Instructions

Replay a previously recorded gameplay session

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": {
      "recording_path": "<recording_path>"
    },
    "name": "replay_gameplay"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoPlayback speed multiplier (default: 1.0)
recording_pathYesPath to the recording file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the replay is run in editor or game, whether it modifies state, or any required setup.

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?

Extremely concise at one sentence. However, it could benefit from a bit more detail without sacrificing conciseness.

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

Completeness2/5

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

For a tool that replays gameplay, the description lacks context about side effects, prerequisites (e.g., a scene open), or how the replay is performed.

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 description coverage is 100%, so the schema already documents the parameters. The description adds no additional meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'replay' and resource 'gameplay session'. However, it does not differentiate from sibling tool 'replay_recording', which could be seen as similar.

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?

No guidance on when to use this tool versus alternatives like 'record_gameplay' or 'replay_recording'. No conditions or exclusions are provided.

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