Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

focus_node

Centers and frames a node by path in the Godot 2D/3D viewport so you can locate and inspect scene objects without manual navigation.

Instructions

Focus/frame a node in the 2D/3D viewport.

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": {
      "node_path": "<node_path>"
    },
    "name": "focus_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the node to focus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether camera state changes, whether selection changes, how 2D vs 3D framing differs, or what happens with an invalid path. 'Focus' and 'frame' are also used interchangeably without clarifying whether they are the same behavior.

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?

One short sentence with no filler and the action front-loaded. It is terse to the point of under-specification, but no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, non-destructive viewport tool with a fully documented schema there is not much the description must cover. Still, with no annotations and no output schema, the agent gets no information about side effects on selection or camera, leaving a noticeable gap.

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% and the single parameter is already documented as 'Path of the node to focus', so there is little room to add value. The description adds no path format, no root-relative vs absolute guidance, and no example.

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?

States a specific verb ('Focus/frame') and resource ('a node') plus the effect location ('in the 2D/3D viewport'), so the agent knows this is a camera/viewport operation. It does not however differentiate itself from nearby siblings like select_node, leaving mild ambiguity about whether focusing also selects.

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 guidance, no exclusions, and no mention of how this differs from select_node or find_game_node. The only implied usage is 'when you want to see a node in the viewport', which the agent has to infer.

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