Skip to main content
Glama
kimimgo

viznoir

by kimimgo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

streamlines

Create streamline visualizations of vector fields from simulation data to analyze flow patterns and direction.

Instructions

Create a streamline visualization for vector fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to simulation file
vector_fieldYesName of the vector field (e.g., "U")
seed_point1NoStart of seed line [x, y, z]
seed_point2NoEnd of seed line [x, y, z]
seed_resolutionNoNumber of seed points
max_lengthNoMaximum streamline length
colormapNoColor map presetCool to Warm
cameraNoCamera presetisometric
purposeNoResolution preset — "analyze" (480p), "preview" (720p), "publish" (1080p)analyze
widthNoOverride width in pixels (must set both width and height, or neither)
heightNoOverride height in pixels (must set both width and height, or neither)
timestepNoTimestep selection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.8.0
    • addedInput schema / properties / camera / description
      Added value: +"Camera preset"
    • addedInput schema / properties / colormap / description
      Added value: +"Color map preset"
    • addedInput schema / properties / file_path / description
      Added value: +"Path to simulation file"
    • addedInput schema / properties / height / description
      Added value: +"Override height in pixels (must set both width and height, or neither)"
    • addedInput schema / properties / max_length / description
      Added value: +"Maximum streamline length"
    • addedInput schema / properties / purpose / description
      Added value: +"Resolution preset — \"analyze\" (480p), \"preview\" (720p), \"publish\" (1080p)"
    • addedInput schema / properties / seed_point1 / description
      Added value: +"Start of seed line [x, y, z]"
    • addedInput schema / properties / seed_point2 / description
      Added value: +"End of seed line [x, y, z]"
    • addedInput schema / properties / seed_resolution / description
      Added value: +"Number of seed points"
    • addedInput schema / properties / timestep / description
      Added value: +"Timestep selection"
    • addedInput schema / properties / vector_field / description
      Added value: +"Name of the vector field (e.g., \"U\")"
    • addedInput schema / properties / width / description
      Added value: +"Override width in pixels (must set both width and height, or neither)"
  2. First observedv0.7.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as output format, error handling, or side effects. It is minimal and provides no assurance of safety or performance.

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 a single sentence with no wasted words, but front-loading could be improved by including key behavioral context.

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

Completeness2/5

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

Despite a rich schema, the description lacks details about the tool's output, which is not defined by an output schema. It does not address integration with sibling tools or typical use cases.

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?

The input schema covers all 12 parameters with descriptions, achieving 100% coverage. The description adds no additional parameter meaning, so baseline score of 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?

The description clearly states the action (create) and the specific resource (streamline visualization for vector fields), distinguishing it from sibling tools like contour, volume_render, and preview_3d.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No usage guidance is provided; the description does not specify when to use this tool over others or mention any prerequisites or exclusions.

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