Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_volume_info

Inspect volume or VDB primitives to report per-volume statistics and optionally analyze voxel distribution via threshold or bins. Identify non-empty density fields before wiring solver sourcing.

Instructions

Per-volume name, resolution, active voxels, value range, mean and sum.

A primitive count cannot tell a correctly named non-empty density field from an empty one, which is the question worth asking before wiring a solver's sourcing. This is the SOP counterpart of get_cop_vdb.

threshold or bins read the voxels (VDB: active ones) for percentiles, a histogram, the count over threshold and box_above_threshold, the world box of the voxels over it: where the smoke is, not where the grid is.

Args: node_path: SOP node path holding volume or VDB primitives. max_volumes: Cap on volumes reported. threshold: Split the voxels at this value and box the ones above it. bins: Histogram bin count, or a list of bin edges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
binsNo
node_pathYes
thresholdNo
max_volumesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bins
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    }
+  ],
+  "default": 0,
+  "title": "Bins"
+}
    • addedInput schema / properties / threshold
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Threshold"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers real behavioral detail: it explains what threshold and bins actually do to the voxels (percentiles, histogram, count over threshold, box_above_threshold, world box of the above-threshold voxels). That is substantive operation-level transparency beyond what any structured field provides.

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 return-value list is well front-loaded, but the middle paragraphs are dense and awkwardly phrased ('threshold or bins read the voxels ... for percentiles, a histogram, the count over threshold and box_above_threshold'), packing too many clauses into one run-on sentence. The Args block is tidy, so structure is adequate but not crisp.

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?

With no output schema and no annotations, the description takes on the return-value and behavioral burden and does so adequately: it enumerates outputs and explains threshold/bins semantics. Minor incompleteness remains around max_volumes behavior and output shape when threshold is unset, but the core is covered.

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, and the Args block documents all four parameters: node_path (SOP path holding volume/VDB primitives), max_volumes (cap), threshold (split value + boxing), and bins (bin count or edge list, matching the anyOf schema). This meaningfully compensates for the schema gap, though the interaction of threshold with the default output is not fully spelled out.

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 and enumerates exactly what is returned (name, resolution, active voxels, value range, mean, sum), and distinguishes itself from get_geometry_info by explaining that primitive counts mislead for density fields. The sibling comparison to get_cop_vdb is also explicit. Clear, but slightly obscured by dense prose.

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?

It gives context ('the question worth asking before wiring a solver's sourcing') and names get_cop_vdb as a related counterpart, which implies when it is used. However it never explicitly states when to prefer this over sample_volume, get_geometry_info, or get_cop_vdb, so usage is inferred rather than directed.

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