Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

capture_frames

Captures multiple screenshots from a running Godot game at a configurable interval and frame count, enabling visual monitoring and debugging of gameplay.

Instructions

Capture multiple screenshots from the running game at a given interval.

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of frames to capture (default: 1)
intervalNoSeconds between captures (default: 0.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full behavioral burden. It does not disclose whether capture blocks, where screenshots are saved, what is returned, what side effects occur, or whether the game must be in a particular state.

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?

A single front-loaded sentence with no repeated or wasted wording. It is terse but appropriately sized for stating the core action.

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 an unannotated capture tool with no output schema, the definition is incomplete. It leaves key agent-relevant behavior unexplained, including return values, file handling, blocking behavior, and prerequisites.

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 both count and interval are already documented in the schema. The description adds only that multiple frames are captured at an interval, without extra format, default, or constraint details beyond the schema.

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?

States a specific verb and resource: 'Capture multiple screenshots from the running game' and adds interval timing. The core action is clear, but it does not distinguish itself from related frame-capture siblings such as start_frame_capture or stop_frame_capture.

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?

There is no explicit when-to-use guidance, no exclusions, and no alternatives named. The description implies periodic capture but does not say when an agent should choose this over continuous start/stop capture tools.

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