Skip to main content
Glama

create_streamtube_3d

Generates an interactive 3D streamtube plot of vector field trajectories, encoding flow magnitude via tube diameter. Visualize wind corridors, ocean currents, or magnetic field lines from grid data.

Instructions

Interactive 3D streamtube plot of a vector field's flow (WebGL, orbit-able).

Integrates the (u, v, w) vector field into streamlines rendered as tubes whose diameter encodes local flow magnitude. Distinct from create_cone_3d (one discrete arrow per sample): a streamtube shows the integrated trajectories — wind corridors, ocean currents, magnetic field lines — rather than the instantaneous direction at each point. The streamline integration runs client-side at render, so a sampled grid needs no SciPy or iterative solver.

Ideal for: wind / ocean circulation, ventilation or HVAC airflow, magnetic / electric field lines, any continuous flow domain where the path of the flow matters more than the per-point arrow.

Returns: {filepath, title, rows}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesRow dicts (one per field-sample point, ideally on a (x, y, z) grid)
themeNo'dark', 'light', or 'professional'dark
titleNoChart title
sizerefNoTube radius scale factor (larger = thicker tubes)
filenameNoOutput filename (without .html)streamtube_3d
u_columnYesColumn for the vector X component
v_columnYesColumn for the vector Y component
w_columnYesColumn for the vector Z component
x_columnYesColumn for the field-sample X position
y_columnYesColumn for the field-sample Y position
z_columnYesColumn for the field-sample Z position (depth)
colorscaleNoPlotly colorscale name for flow-magnitude mappingViridis

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses that the plot is interactive (WebGL, orbit-able), integrates client-side, and returns filepath/title/rows. However, it does not cover potential behaviors like data size limits or rendering performance considerations.

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?

Concise and well-structured: purpose sentence, integration explanation, contrast with sibling, ideal use cases, and return information. Every sentence adds value without redundancy.

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?

Given the complexity (12 params, 7 required) and the presence of an output return description, the description is fairly complete. It explains the concept, differentiates from similar tools, and provides use case guidance. Minor gap: no explicit mention of data format expectations beyond 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?

Input schema has 100% coverage with descriptions for all parameters. The description adds context about diameter encoding local flow magnitude, but this is more about behavior than parameter meaning. Schema descriptions are sufficient, so baseline 3 is appropriate.

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?

Clearly states the tool creates an interactive 3D streamtube plot of a vector field's flow, using specific verbs ('create') and a specific resource ('streamtube 3d plot'). Explicitly distinguishes from the sibling 'create_cone_3d' by explaining the difference between integrated trajectories and discrete arrows.

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 ideal use cases (wind, ocean currents, magnetic field lines) and contrasts with the sibling tool. However, does not explicitly state when not to use the tool or list alternatives beyond the one sibling mentioned.

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