Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_camera_3d

Add a Camera3D node to a Godot scene with optional property overrides and parent path, enabling AI-driven game development setup.

Instructions

Add a Camera3D node to the scene with optional configuration.

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": "setup_camera_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertiesNoCamera property overrides
parent_pathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 burden and does not say whether this mutates the scene irreversibly, what happens if a camera already exists, what defaults a Camera3D gets, or whether an editor scene context is required. Only 'optional configuration' hints that both parameters may be omitted.

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 no filler. It is efficient, though its brevity borders on under-specification for a scene-mutating 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?

For a scene-mutating tool with no annotations, no output schema, and an opaque nested properties object, the description omits return behavior, existing-node handling, and defaults. It leaves too much for the agent to infer before calling it.

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 coverage is 100%, so both properties are documented and the baseline is a 3. However, the nested 'properties' object is described only as 'Camera property overrides' with no indication of which camera fields are valid, and the description adds nothing beyond the schema.

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: 'Add a Camera3D node to the scene.' This distinguishes it from generic node-creation siblings such as add_node and from setup_* tools that configure existing nodes, though it never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

The description implies when to use it (when a camera is needed in the scene) and notes configuration is 'optional,' but it gives no when-not guidance and never names the generic add_node alternative for non-camera nodes.

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