Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_render_info

Retrieve rendering information from the running game, such as render time and object count, to monitor performance and diagnose rendering issues.

Instructions

Get rendering information from the running game (render time, object count, 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_render_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does identify the kind of data returned and that the game must be running. However, it says nothing about failure behavior when no game is running, whether the call is a cheap read, or how the snapshot is sampled, leaving real gaps for an unannotated tool.

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?

A single front-loaded sentence with no wasted wording. The trailing 'etc.' weakens precision slightly by leaving the returned field set open-ended, which is the only real flaw.

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?

For a no-parameter read tool with no output schema, the description should at least bound what 'rendering information' covers and how it differs from the performance siblings. It gives examples but trails off into 'etc.', leaving the return contents and the overlap with get_game_performance unresolved.

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 zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description adds nothing that is needed 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?

The description states a specific verb and resource ('Get rendering information from the running game') and gives concrete examples of the returned metrics (render time, object count). It is clear what the tool does, but it does not distinguish itself from the numerous get_game_* siblings, notably get_game_performance, which plausibly covers render time as well.

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 and no alternative named. 'From the running game' hints at a prerequisite, but the agent is left to infer when this is preferable to get_game_performance or get_editor_performance, and no exclusions are stated.

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