Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_performance

Retrieve real-time performance metrics from a running Godot game, including FPS, memory usage, and draw calls, to diagnose bottlenecks and guide optimization.

Instructions

Get performance monitor values from the running game (FPS, memory, draw calls, etc.).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It hints that a game must be running, but says nothing about whether values are a live snapshot or sampled, how often they refresh, what happens if the game is paused or absent, or whether the call is read-only. For a zero-annotation tool this is a meaningful gap.

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 the resource and scope stated immediately and no filler. The metric examples earn their place by telling the agent what kind of data to expect.

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

Completeness3/5

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

With no parameters and no output schema, the description is the only source of return-value information, and it provides only a partial list plus 'etc.'. It does not say which monitors exist, whether all are returned at once, or the shape of the response, though the low complexity of a no-arg read keeps this from being severe.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter semantics to document and the baseline of 4 applies. The listed metrics (FPS, memory, draw calls) describe output rather than inputs, which is helpful but not required here.

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 ('Get') and resource ('performance monitor values') and scopes it with 'from the running game', which implicitly separates it from the editor-side sibling. It also names concrete metrics (FPS, memory, draw calls), so an agent knows roughly what data comes back. It does not explicitly contrast with get_editor_performance or get_performance_monitors, leaving some differentiation to inference.

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 when-to-use guidance, no statement of prerequisites beyond the embedded phrase 'running game', and no routing to alternatives such as get_editor_performance or get_performance_monitors. An agent must infer the choice from the tool name and the word 'game'.

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