Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_pause

Pause or resume the running Godot game by setting its paused state, letting you inspect or debug gameplay without stopping execution.

Instructions

Pause or unpause the running game

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

Input Schema

NameRequiredDescriptionDefault
pausedNoTrue to pause, false to unpause. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior2/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 states the action but does not explain whether the pause is a toggle or a set operation, what happens if the game is already paused or not running, or how this affects game loop execution.

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 a single focused sentence that immediately conveys the action. There is no redundant phrasing, filler, or repeated information from the schema.

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 simple one-parameter runtime control, the description plus schema is nearly sufficient for an agent to invoke it correctly. It is somewhat thin on behavioral side-effects and usage context, but the low complexity of the tool means not much more is strictly required.

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%: the paused parameter is fully described in the schema with its meaning and default. The tool description adds no additional parameter context, but the schema already provides sufficient semantics, so the baseline score of 3 applies.

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 a specific action ('pause or unpause') and resource ('the running game'), making it distinguishable from stop/start tools. It does not explicitly differentiate itself from related runtime controls like game_time_scale or game_process_mode, but the core purpose is unambiguous.

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 is given about when to use this tool versus alternatives such as stop_project, game_time_scale, or game_wait. The phrase 'running game' implies it applies during an active session, but there are no explicit conditions, exclusions, or preferred scenarios.

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