Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_current_network

Navigate the network editor to a network; the viewer follows it in.

Instructions

Navigate the network editor to a network; the viewer follows it in.

Call it on the network you build in. By default the viewer then hides every other object (the viewport's Y hotkey, no display flag touched), so the work is seen on its own and the rest of the scene does not cook.

A DOP network becomes the current one, where DOP shelf tools build (the reply names current_dop_network), as entering it in Houdini does; with other_objects=None that is all it changes besides the editor.

A Visible Objects pattern (saved with the hip) that leaves this object out is set back to "*", named in visible_objects_reset.

A node that is not a network (a SOP) is made current in its own network, named in entered and current_node.

Args: network_path: Network path to navigate to. other_objects: "hide" (default), "ghost", "show", or null to leave the viewer as it is.

Input Schema

NameRequiredDescriptionDefault
network_pathYes
other_objectsNohide

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.21.0
    • addedInput schema / properties / other_objects
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "hide",
+  "title": "Other Objects"
+}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses that other objects get hidden by default, that no display flag is touched, that a Visible Objects pattern may be reset to '*', that DOP networks become current, and that non-network nodes enter their own network. It even names the reply keys that report each side effect.

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 action, and the side-effect details each add distinct value. The prose is somewhat sprawling with awkward line breaks and parentheticals, but no sentence is filler.

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 2-param mutation tool with no annotations and no output schema, the description covers side effects and return keys thoroughly. It omits failure behavior (invalid paths, whether the editor must already be open) and doesn't clarify transition rules between contexts.

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 description coverage is 0%, so the description must compensate; it does for other_objects by enumerating 'hide' (default), 'ghost', 'show', and null with the behavioral consequence of each. network_path is only glossed as 'Network path to navigate to', which is the remaining gap.

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 and resource: 'Navigate the network editor to a network' with the viewer following. It also spells out what 'current' means across contexts (DOP network, ordinary SOP). It never names a sibling alternative, so it doesn't fully distinguish itself from tools like set_viewer_context or set_selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call it on the network you build in' gives clear usage context, and the other_objects=null case explains when to leave the viewer untouched. There is no explicit 'do not use this when...' or named alternative, so guidance is contextual rather than complete routing.

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