Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_mesh_instance

Adds a MeshInstance3D with a primitive mesh to a Godot scene, allowing parent path, node name, and property overrides.

Instructions

Add a MeshInstance3D with a primitive mesh to the scene.

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": {
      "mesh_type": "<mesh_type>"
    },
    "name": "add_mesh_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNode name
mesh_typeYesMesh type (BoxMesh, SphereMesh, CylinderMesh, etc.)
propertiesNoAdditional property overrides
parent_pathNoParent node path

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?

With no annotations, the description carries the full behavioral burden and does not meet it. It never says whether the node is added to the currently edited scene, what happens when parent_path is omitted, whether the operation is undoable, or whether it can fail (e.g., invalid mesh_type). Mutation semantics are entirely implicit.

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 zero filler, which is structurally clean. It is arguably under-sized for a mutating tool with a nested-object parameter, so conciseness is achieved at the cost of substance.

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?

For a scene-mutating tool with four parameters (including a nested free-form properties object), no annotations, and no output schema, the definition is too thin. Key facts an agent needs — insertion target defaults, return value, failure modes — are absent.

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 description coverage is 100%, so the schema already documents all four parameters; the description's phrase "primitive mesh" only reinforces that mesh_type takes primitive types. No added meaning is given for the nested "properties" override object or for how parent_path interacts with the default insertion point.

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 ("Add") and a specific resource ("MeshInstance3D with a primitive mesh"), and the schema's mesh_type examples make the scope concrete. It does not, however, distinguish itself from close siblings such as add_scene_instance or add_node, so an agent must guess which one to reach for.

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 at all: no mention of when to prefer this over add_node or add_scene_instance, no prerequisites (e.g., an open scene, editor context), and no exclusions. The agent must infer applicability purely from the one-line purpose.

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