Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_game_screenshot

Capture screenshots of running Godot games to verify visual output, debug rendering issues, and inspect gameplay states through AI assistants.

Instructions

Capture running game screenshot. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden of behavioral disclosure. 'Compatibility tool' likely refers to Godot's Compatibility rendering backend but is unexplained. No disclosure of output format (file path, base64, bytes), blocking behavior, or side effects on the running game.

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 brief at two fragments with main purpose front-loaded. However, '(Compatibility tool)' is cryptic and reads as insufficiently informative rather than purposefully concise—it suggests important behavioral context but fails to elaborate.

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?

Inadequate for a tool with undocumented parameters and no output schema. Missing explanation of return value format (critical for a screenshot tool), parameter effects on connection behavior, and what constitutes a 'running game' state.

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

Parameters1/5

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

Input schema has 0% description coverage for 'timeoutMs' and 'autoConnect'. The description adds no semantics for these parameters, leaving critical configuration options (connection timeout duration, auto-connection to game instance) completely undocumented despite having no schema descriptions to fall back on.

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 provides a specific verb ('Capture') and resource ('running game screenshot'), clearly distinguishing it from sibling tool 'get_editor_screenshot' by specifying 'running game'. The parenthetical '(Compatibility tool)' is vague but doesn't obscure the core purpose.

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 explicit when-to-use guidance, comparison to alternatives (e.g., 'get_editor_screenshot', 'capture_frames'), or prerequisites (e.g., game must be running). The '(Compatibility tool)' tag hints at specific rendering backend context but lacks explanation of when this matters.

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