Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_selected_nodes

Retrieve the list of nodes currently selected in the Godot editor so commands can target the user's active selection.

Instructions

Get the list of currently selected nodes in the editor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full disclosure burden, yet it only restates the purpose. It says nothing about whether this reads live editor state versus game runtime, what happens when the selection is empty, or whether the call has any side effects — for a state-read tool with zero annotation coverage this leaves meaningful gaps.

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 or redundant phrasing. It is as tight as it can be for the information it chooses to convey, though the tightness comes partly from omitting detail rather than from disciplined editing.

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?

With zero parameters and no output schema, the tool is simple, but the description never indicates what the returned list contains (node paths, names, identifiers) or how an empty selection surfaces. That return-shape detail is the main thing an agent would still need before calling confidently.

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

Parameters4/5

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

The input schema has no parameters at all, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste words inventing parameters.

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 pairs a specific verb (get) with a specific resource (currently selected nodes in the editor), which is unambiguous about what it returns. It does not, however, contrast itself with adjacent readers like get_node_properties or get_current_scene, so the agent must infer the boundary from the names alone.

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 explicit when-to-use statement and no mention of alternatives such as inspecting properties of a known node versus discovering what the user has selected. The word 'currently' faintly implies a live-editor context, but nothing tells the agent when this tool is the right choice over its siblings.

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