Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_node

Add nodes to Godot scenes by defining types and properties via MCP. Enables AI assistants to programmatically create scene elements for automated game development.

Instructions

Add node with type and optional properties. (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_node"
  }
}

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?

No annotations provided, so description carries full disclosure burden. The 'Compatibility tool' note adds minimal behavioral context (legacy/deprecated status), but the description fails to state whether this is destructive, requires an open scene, or what happens on timeout.

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?

Extremely brief single sentence. While efficiently worded, it is underspecified given the complete lack of schema documentation and annotations; it prioritizes brevity over necessary detail.

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 this is a mutation tool (adds nodes) with zero annotations, no output schema, and 0% parameter description coverage in a complex Godot environment with many specialized alternatives, the description is inadequate. It should explain the additionalProperties contract and timeout behavior.

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

Parameters2/5

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

Schema has 0% description coverage for timeoutMs and autoConnect. The description mentions 'optional properties' which aligns with additionalProperties: true, but completely ignores the two explicit parameters defined in the schema, leaving their purpose undocumented.

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?

States 'Add node' which is clear, but references 'type' which is absent from the schema properties (only additionalProperties: true exists), creating confusion about how to specify the node type. Fails to distinguish from specific sibling tools like add_mesh_instance or add_gridmap.

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?

Provides only the parenthetical '(Compatibility tool)' as usage context, but offers no explicit guidance on when to use this generic add_node versus the specialized add_* siblings (add_animation_track, add_mesh_instance, etc.) or prerequisites.

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