Skip to main content
Glama

Create dome output

create_dome_output

Remap a panoramic equirectangular source into a square dome master for planetarium fulldomes using fisheye or equirectangular projection.

Instructions

Remap a source TOP (treated as an equirectangular / panoramic master) into a square single-output dome master for planetarium fulldomes / 360 — the curved complement to create_multi_output's flat tiling. A Select TOP pulls the master in, a GLSL TOP warps it (fisheye: equirect → centred dome disc using fov; equirectangular: near-passthrough identity remap) via a shader held in a Text DAT, ending on a Null ready for setup_output. Creates a new baseCOMP under parent_path holding the Select TOP, GLSL remap, and Null output. With expose_controls a Rotation knob spins the dome horizon. Note: this GLSL-remaps an existing flat source — use create_cubemap_dome instead for a true cube-map render (higher fidelity, no equirect pole-pinch/seam). Returns a summary plus a JSON block with the container path, created node paths, the output path, exposed controls, any node errors, warnings (including the cubemap-follow-up note), and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_pathYesThe master TOP to remap, treated as an equirectangular / panoramic source (the full 360°×180° latlong image the dome warps from).
projectionNofisheye: warp the equirectangular source into a centred dome disc (planetarium fulldome master). equirectangular: near-passthrough identity remap, so an already-equirect source still yields a valid output.fisheye
resolutionNoSquare dome-master resolution (width = height).2048
fovNoFisheye coverage in degrees (the angular diameter the disc spans). 180 = full hemisphere (standard fulldome); larger over-fills, smaller zooms in. Used by the fisheye shader.
expose_controlsNoWhen true (default), expose a Rotation knob bound to the shader uniform that spins the dome horizon (degrees).
parent_pathNoParent network where the dome-output container is created (default '/project1')./project1
Behavior4/5

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

Description details what happens: creates a baseCOMP with Select TOP, GLSL remap, Null output. Exposes controls like Rotation knob. Annotations (readOnlyHint=false, destructiveHint=false) align with creation behavior. Could add more about error handling but sufficient.

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?

Well-structured with front-loaded action and clear breakdown. However, it is somewhat lengthy (5 sentences). Could be trimmed slightly without losing clarity.

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?

Given the complexity (6 params, no output schema), the description covers purpose, internal nodes, output format (summary with JSON block), and includes warnings. No gaps identified.

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 100% with descriptions. Description adds value by explaining projection modes (fisheye vs equirectangular) and fov coverage in context. Slightly beyond repetition.

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 tool's purpose: remapping a source TOP into a dome master for planetarium fulldomes. It distinguishes itself from sibling create_multi_output (flat tiling) and create_cubemap_dome (cube-map render).

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

Usage Guidelines5/5

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

Provides explicit when-to-use (dome/fulldome output) and when-not-to-use (use create_cubemap_dome for higher fidelity). Names specific alternative tools and explains trade-offs.

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/Pantani/tdmcp'

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