Skip to main content
Glama

set_geometry_node_input

Sets a geometry node input value in Blender by group, node, and input name to adjust procedural geometry.

Instructions

Set a geometry node input value.

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": {
      "group_name": "<group_name>",
      "node_name": "<node_name>",
      "input_name": "<input_name>",
      "value": "<value>"
    },
    "name": "set_geometry_node_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
node_nameYes
group_nameYes
input_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 burden. It does not say whether the value is coerced to the socket's type, what happens if the group/node/input name is invalid, or whether the change is undoable — significant omissions for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but its brevity comes at the cost of under-specification rather than tight editing. It is front-loaded but thin.

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?

An output schema exists, so return values need not be described. However, for a four-parameter mutation with zero annotation coverage and zero schema descriptions, the definition leaves too much unspecified to call reliably.

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 description coverage is 0% across four required parameters. The description's phrasing loosely maps to group_name/node_name/input_name/value, but adds nothing about the untyped 'value' field — the agent is not told it must match the target input socket's data type.

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 names a specific verb and resource: 'Set a geometry node input value,' which tells an agent exactly what changes. It offers no differentiation from siblings such as connect_geometry_nodes or add_geometry_node, which is the only thing keeping it from a 5.

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 guidance on when to use this versus the many other geometry-node tools, and no stated prerequisites (e.g., that the node group and node must already exist). The agent must infer all preconditions from the sibling list.

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