Skip to main content
Glama
Sign In

AI Game Developer: MCP for Unity, Unreal and Godot

by io.github.IvanMurzak
OverviewDiscussionsAdmin

Enroll engine plugin

enroll_engine_plugin

Start connecting a new game engine to your account. Returns a one-time enrollment code with instructions for installing the engine plugin.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engine": "<engine>"
    },
    "name": "enroll_engine_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
engineYesIdentifier of the engine plugin to enroll, as the plugin's host documents it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true; the description adds the key context that the result is a one-time code plus install instructions, which explains the non-idempotent nature. It does not mention code expiry, whether re-enrolling replaces a prior enrollment, or any permission requirements, so it is not fully transparent.

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?

Two sentences, front-loaded with the action and followed by the return value. No filler or repetition of the title.

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 single-parameter tool with no output schema, the description covers both the action and what comes back (one-time code with instructions). Missing only guidance on the surrounding enrollment flow and code lifetime, which would make it fully complete.

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 coverage is 100% and the single `engine` parameter is documented in the schema itself, so the description carries no additional burden. The description adds only that the engine is a 'new game engine', which does not extend the schema's meaning; baseline 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?

States a specific verb and resource: begin enrolling a game engine and receive a one-time enrollment code with install instructions. It is clearly distinguishable from list_engine_instances and select_engine_instance by resource and effect, though it does not explicitly name those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start connecting a new game engine' implies this is the first step in an enrollment flow, but the description never states prerequisites, when to prefer it over the sibling tools, or what to do after receiving the code. Usage is implied rather than guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AI Game Developer: MCP for Unity, Unreal and Godot toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources