Skip to main content
Glama

create_multimesh

Create a Godot MultiMesh resource file (.tres) with configurable mesh, instance count, and transform mode for efficient rendering of repeated geometry.

Instructions

Create a MultiMesh .tres resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesOutput path for new MultiMesh .tres (e.g. "meshes/grass_multimesh.tres")
mesh_pathNoOptional .tres Mesh path (res://...) to assign
instance_countNoNumber of instances to allocate
transform_modeNoTransform formattransform_3d
Behavior2/5

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

No annotations are available, so the description must disclose behavioral details. It only states the creation action without mentioning side effects like file overwriting, directory creation, or project registration. This is a significant transparency gap for a mutation tool.

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 wasteful words. It is concise and easy to scan, though slightly under-specified for a tool with four parameters.

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 creation tool with no annotations and no output schema, the description should provide more context about the resource's purpose or side effects. It only states the resource type, leaving the agent to infer behavior from the schema alone. This is insufficient for a fully informed invocation.

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 fully documents all parameters. The description adds no additional parameter context beyond what the schema already provides, earning the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and the specific resource type ('MultiMesh .tres'), which is distinct from generic create_resource or write_resource tools. It unambiguously identifies the tool's purpose.

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 description provides no guidance on when to use this tool versus alternatives like create_resource or write_resource. No contextual hints or exclusions are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yanhuifair/Godot-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server