Skip to main content
Glama

create_volume_3d

Render a 3D volume from scattered scalar field samples to visualize interior distributions like pollution or temperature, with configurable opacity and iso-surfaces.

Instructions

Interactive 3D volume render of a volumetric scalar field (WebGL, orbit-able).

Renders the full semi-transparent scalar field across (x, y, z) — a see-through cloud whose density + color encode value_column, with a configurable number of internal iso-surfaces. Distinct from create_isosurface_3d (which draws only the single boundary where value equals a threshold): a volume shows the interior distribution of the field, not just its level-set shell. The ray-marched rendering runs client-side, so scattered samples are accepted without a regular grid or SciPy.

Ideal for: 3D pollution / concentration clouds, temperature or humidity fields across a monitoring volume, groundwater head distributions, any scalar field where the interior structure — not just the boundary — matters.

Returns: {filepath, title, rows}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesRow dicts (one per volumetric sample point)
themeNo'dark', 'light', or 'professional'dark
titleNoChart title
isomaxNoUpper scalar bound (defaults to column max)
isominNoLower scalar bound (defaults to column min)
opacityNoVolume opacity (0–1); keep low so the interior stays legible
filenameNoOutput filename (without .html)volume_3d
x_columnYesColumn for the X axis
y_columnYesColumn for the Y axis
z_columnYesColumn for the Z axis (depth)
colorscaleNoPlotly colorscale name for value mappingViridis
show_surfaceNoFalse = pure translucent cloud (no internal surfaces)
value_columnYesColumn whose values fill the volume
surface_countNoNumber of internal iso-surfaces drawn inside the volume

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but description explains ray-marched rendering runs client-side, accepts scattered samples, and returns filepath/title/rows. Does not mention side effects, but as a create tool, it’s implicitly creating a file.

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?

The description is well-structured with a lead sentence, technical detail, sibling differentiation, and ideal use cases. Slightly verbose but every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 14 params and 5 required, the description covers purpose, behavior, rendering method, ideal use, and return values comprehensively, given the 100% schema coverage and output schema.

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

Parameters3/5

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

Schema has 100% coverage with descriptions for all parameters. Description adds minor context (e.g., 'configurable number of internal iso-surfaces') but does not significantly enrich beyond schema.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it renders an interactive 3D volume of a scalar field, using specific verbs like 'render' and 'see-through cloud', and explicitly distinguishes itself from the sibling tool create_isosurface_3d.

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?

Provides clear ideal use cases (pollution clouds, temperature fields) and contrasts with isosurface for when only boundaries matter. Lacks explicit when-not-to-use, but the contrast is strong enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/acailic/serbian-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server