Skip to main content
Glama

get_node_properties

Read-only

Read current property values of one or more nodes from a Godot scene file in a single process, optionally returning only properties that differ from class defaults.

Instructions

Read the current property values of one or more nodes from a scene file, in one Godot process. Always-array: pass a one-element nodes array for one node. Per-node changedOnly: true leaves out properties that match the class defaults. Returns: results[] in input order: { nodePath, nodeType, properties }, or { nodePath, error } when not found. Values use the input shapes of set_node_properties. warnings leads when changedOnly had no defaults to compare. Errors if the scene cannot be loaded.

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>",
      "nodes": "<nodes>"
    },
    "name": "get_node_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesNodes to read properties from
scenePathYesScene file path relative to the project
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
resultsYes
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "error": {
      +            "type": "string"
      +          },
      +          "nodePath": {
      +            "type": "string"
      +          },
      +          "nodeType": {
      +            "type": "string"
      +          },
      +          "properties": {
      +            "type": "object"
      +          }
      +        },
      +        "required": [
      +          "nodePath"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "warnings": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description goes well beyond that: it discloses result ordering, the per-node error object shape, that errors occur when the scene cannot be loaded, and where warnings appear in the response. It doesn't cover permissions, large-scene performance, or partial-failure semantics across the node array, so not a 5.

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?

Front-loaded with the core purpose and packed with density — no filler sentences. A few clauses are compressed to the point of awkwardness ('warnings leads when changedOnly had no defaults to compare'), which slightly hurts first-pass comprehension.

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

Completeness4/5

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

For a 3-required-param read tool with an output schema and readOnly annotation, this is nearly complete: purpose, array handling, filtering semantics, return ordering, and error behavior are all present. Remaining gaps are minor — no guidance on cross-node partial failure or when to choose this over sibling read tools.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by explaining that changedOnly drops properties matching class defaults and that it also drives the warnings field when no defaults exist. The 'always-array' note adds calling guidance for the nodes parameter that the schema alone does not emphasize.

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

Purpose5/5

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

States a specific verb and resource — 'Read the current property values of one or more nodes from a scene file' — plus a scope qualifier ('in one Godot process') and a reference to the counterpart writer, set_node_properties. An agent can immediately distinguish this read tool from set_node_properties and from structural tools like get_scene_tree.

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?

Usage is implied rather than spelled out: reading properties is obviously a read, and 'pass a one-element nodes array for one node' clarifies the calling shape. There is no explicit when-to-use/when-not guidance or named alternative (e.g. when to prefer get_scene_tree or get_node_signals instead), so the agent must infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.