Skip to main content
Glama

get_volume_info

Reports per-volume name, resolution, active voxels, value range, mean and sum, plus threshold and histogram stats to confirm a density field is non-empty 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.

voxel_size, first_voxel_center and last_voxel_center place the grid (a VDB's: its active voxels): two volumes share a grid when all three match, which their bboxes cannot tell.

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.

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": {
      "node_path": "<node_path>"
    },
    "name": "get_volume_info"
  }
}

Input 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.9/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 does substantial work: it explains that threshold/bins actually read voxels (active voxels for VDBs) to compute percentiles, histograms, counts over threshold, and the world box of qualifying voxels, and that voxel_size plus first/last voxel center determine grid identity where bounding boxes cannot. It never states read-only-ness or cost implications of scanning large volumes, which is the main remaining gap.

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 content is useful but poorly front-loaded: it opens with a verbless field fragment, then two discursive paragraphs, and only ends with an Args block that repeats some of the body. Phrases like 'which is the question worth asking before wiring a solver's sourcing' add flavor more than information.

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 four-parameter inspection tool with no output schema and no annotations, the description covers what to pass, what per-volume figures come back, and what the optional threshold/bins modes produce. What is missing is output shape (per-volume records vs. text) and the semantics of the zero/null defaults.

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 Args block is doing real work: node_path is scoped to SOP nodes holding volume or VDB primitives, max_volumes is described as a cap on volumes reported, threshold as the split value that also boxes voxels above it, and bins as either a count or a list of edges. It does not explain what bins=0 (the default) means, nor the interaction when both threshold and bins are set.

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 opening line names the resource (volumes/VDBs) and enumerates the reported fields — name, resolution, active voxels, value range, mean, sum — and later explicitly positions itself as 'the SOP counterpart of get_cop_vdb', which separates it from a sibling. The verb is only implied ('get' in the name), so it reads as a field list rather than a stated action, which keeps it short of 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 Guidelines4/5

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

It supplies a concrete justification for reaching for this tool: a primitive count cannot distinguish a correctly named non-empty density field from an empty one, which is worth asking before wiring a solver's sourcing. It also names get_cop_vdb as the VDB-context alternative. It stops short of explicit exclusions (e.g., when to prefer sample_volume or get_bounding_box instead).

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