Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_current_network

Navigate Houdini's network editor to a target network path and optionally hide, ghost, or show other objects so the viewer isolates your work without altering display flags.

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.

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

TableJSON 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.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real value: it discloses that other objects are hidden by default (equivalent to the viewport Y hotkey), that no display flag is touched, and that the rest of the scene stops cooking. These are non-obvious side effects an agent could not infer. Return/response behavior is not described, keeping it from 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.

Conciseness5/5

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

Front-loaded with the core action, followed by the usage note and a clean Args block. Every sentence carries information, including the parenthetical about the Y hotkey and the display flag, with no 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 two-parameter tool with no annotations and no output schema, the description covers purpose, default behavior, side effects, and all meaningful parameter values. It could say more about what happens on an invalid path or whether navigation is undoable, but it is sufficient to invoke correctly.

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 0%, so the description must compensate, and it largely does: it enumerates the four meaningful values of other_objects ('hide', 'ghost', 'show', null) with their semantics, which the schema does not provide. network_path is only restated as 'Network path to navigate to', adding little, which caps the score below 5.

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?

Names a specific verb and resource ('Navigate the network editor to a network') and adds the viewer-follow behavior, so an agent knows exactly what happens. It does not, however, distinguish itself from adjacent siblings such as set_viewer_context or set_viewport_display, which is what a 5 would require.

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 condition under which the default hiding behavior applies. There are no explicit exclusions or named alternatives, so it falls short of a 5 but is more than implied guidance.

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