Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_mesh_instance

Add MeshInstance3D nodes with primitive meshes to Godot scenes. Creates basic 3D geometric shapes like cubes or spheres for AI-assisted game development.

Instructions

Add MeshInstance3D with primitive mesh. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only offers the cryptic '(Compatibility tool)' note without explaining what compatibility issues exist, what side effects occur (scene modification, persistence), or why connection-related parameters are present for a mesh creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately brief at two sentences and front-loaded with the core action, but given the 0% schema coverage and parameter mismatch, it is insufficiently informative rather than admirably concise.

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?

Given zero schema descriptions, no annotations, no output schema, and the apparent architectural complexity (remote Godot editor manipulation), the description is inadequate. It fails to explain the connection requirement implied by the parameters or the return behavior.

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

Parameters1/5

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

Schema description coverage is 0% for both timeoutMs and autoConnect parameters, and the description completely fails to compensate by explaining what these connection-related parameters mean in the context of adding a mesh instance, or what values are appropriate.

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 identifies the action (Add), resource type (MeshInstance3D), and specific variant (with primitive mesh), distinguishing it from generic add_node or add_scene_instance siblings. However, it doesn't clarify the execution context (e.g., whether this operates on the active Godot editor instance).

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 provided on when to use this tool versus alternatives like add_node or add_scene_instance, nor any mention of prerequisites such as an active Godot connection despite the presence of autoConnect and timeoutMs parameters.

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