Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

deploy_to_android

Build and deploy a Godot project to a connected Android device using a specified export preset and optional ADB device ID.

Instructions

Build and deploy the project to a connected Android device.

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

Input Schema

NameRequiredDescriptionDefault
presetNoExport preset name to use
device_idNoADB device ID (optional, uses first device)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 and does not meet it. For a build-and-deploy operation it says nothing about duration, whether an existing install is overwritten, what happens on build failure, whether the app is launched afterward, or what state on the device is affected.

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 filler or redundancy. It is efficient, though the terseness is a symptom of the missing behavioral detail rather than a model of structure.

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?

This is a multi-step, potentially long-running operation with side effects on an external device, yet there are no annotations, no output schema, and the description tells the agent almost nothing about outcomes or failure modes. An agent knows what the tool does but not how it behaves or what to expect back.

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%, so preset and device_id are already documented, including the 'optional, uses first device' default. The description adds no meaning beyond the schema, which is the baseline 3 case when the schema does the heavy lifting.

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 names a specific compound verb (build and deploy) plus the resource (the project) and the target (a connected Android device). That is enough to distinguish it from siblings like list_android_devices or get_android_preset_info, though it never names those alternatives explicitly.

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?

The only usage hint is 'connected Android device,' which implies a prerequisite but is not stated as one. There is no guidance on when to pick this over device inspection tools, no mention that a device must already be attached and authorized, and no explanation of when to pass a preset versus relying on a default.

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