Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_particles

Add GPU-accelerated particle effects to Godot scenes by creating GPUParticles2D or GPUParticles3D nodes for smoke, fire, and magic effects.

Instructions

Create GPUParticles2D or GPUParticles3D. (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": "create_particles"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/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. The only behavioral hint is '(Compatibility tool)', which is opaque. No disclosure of what 'create' entails (instantiation in scene, memory implications), nor explanation of the 'additionalProperties': true allowance for extra particle properties.

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

Conciseness2/5

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

While brief at two clauses, the description is insufficiently informative rather than efficiently concise. The '(Compatibility tool)' clause consumes space without earning its place due to lack of explanation. Critical information (parameter meanings, output behavior) is missing entirely.

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 node-creation tool with mysterious parameters and no output schema, the description is inadequate. It fails to explain the parameter semantics, the compatibility aspect, or what properties can be passed via additionalProperties. The agent lacks sufficient context to invoke this tool correctly.

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%, and the description completely omits parameter documentation. The parameters 'timeoutMs' and 'autoConnect' appear unrelated to particle creation (suggesting connection/operation timeouts), creating confusion about the tool's actual mechanism. No compensation for the schema's lack of descriptions.

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

Purpose3/5

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

The description identifies the specific Godot node types created (GPUParticles2D/3D), but the '(Compatibility tool)' parenthetical is cryptic and unexplained. It also fails to distinguish this tool from the generic 'add_node' sibling or explain why specific particle creation tools exist alongside it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 'add_node' or other particle-related siblings like 'apply_particle_preset'. The 'Compatibility tool' label suggests specific usage constraints (perhaps legacy support) but offers no explanation, leaving the agent without selection criteria.

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