Skip to main content
Glama
Godot MCP - Full Control
by cxb2523

game_procedural_mesh

Create custom 3D meshes in Godot from vertex positions, normals, UVs, and triangle indices, turning raw geometry data into ArrayMesh nodes under a chosen parent.

Instructions

Generate meshes via ArrayMesh from vertex data

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": {
      "parentPath": "<parentPath>",
      "vertices": "<vertices>"
    },
    "name": "game_procedural_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
uvsNoUV coordinates [[u,v],...]
nameNoNode name
indicesNoTriangle indices [i0,i1,i2,...]
normalsNoVertex normals [[x,y,z],...]
verticesYesVertex positions [[x,y,z],...]
parentPathYesParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the mesh is generated via ArrayMesh, but does not explain whether a node is created under parentPath, whether it requires the editor or a running game, what the return behavior is, or what failure modes exist.

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?

The description is a single front-loaded sentence with no filler or repetition. It is efficient, though its extreme brevity contributes to the broader under-specification of the tool.

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 6-parameter mesh-creation tool with no annotations and no output schema, so the description needs to carry significant contextual weight. It does not cover scene integration, return behavior, optional array relationships, or error conditions, leaving the definition substantially incomplete.

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 every parameter is already documented in the input schema. The description adds only the phrase 'from vertex data' and does not clarify relationships among vertices, indices, normals, and uvs or constraints such as matching array lengths.

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: generate meshes, using ArrayMesh from vertex data. It is clear enough to distinguish this from tools like game_csg or game_multimesh at a high level, but it does not explicitly name or contrast 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as game_mesh_instance, export_mesh_library, or game_csg. The intended context is only implied by the tool name and the word 'mesh'.

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