Skip to main content
Glama

connect_geometry_nodes

Connect two geometry nodes by linking a source socket to a target socket inside a named node group.

Instructions

Connect two geometry nodes.

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>",
      "from_node": "<from_node>",
      "from_socket": "<from_socket>",
      "to_node": "<to_node>",
      "to_socket": "<to_socket>"
    },
    "name": "connect_geometry_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_nodeYes
from_nodeYes
to_socketYes
group_nameYes
from_socketYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 behavioral burden. It implies a mutation but says nothing about required context (an existing modifier/node group), whether the operation is idempotent, what happens if sockets are incompatible, or whether prior connections are destroyed.

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?

The single sentence is clean and front-loaded with zero filler, but its brevity reflects under-specification rather than economy. There is no structure to organize prerequisites or parameter expectations.

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 explained. Still, for a five-parameter mutation tool with no annotations, the description leaves the agent without the context needed to invoke it correctly, notably socket/node identification format and required preconditions.

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

Parameters1/5

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

Schema description coverage is 0% across five required parameters, and the description contributes no meaning for any of them. An agent gets no help understanding what group_name, from_node, from_socket, to_node, or to_socket should contain (identifiers? names? indices?).

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

Purpose3/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 ('Connect two geometry nodes'), so the action is identifiable. However, it does not differentiate from nearby siblings such as add_geometry_node or set_geometry_node_input, which plausibly also modify node graphs, leaving the agent to infer the distinction.

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 tool versus alternatives, no prerequisites (e.g., that the node group must already exist), and no statement about whether an existing link between the sockets is replaced. Usage must be inferred entirely from the name.

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