Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

crear_skin_vts

Creates native 3DVista .vts skins ready to import, with branded buttons, text, images, and show/hide or navigation actions for custom tour interfaces.

Instructions

Crea un skin NATIVO de 3DVista (.vts) listo para importar: Skin Editor > icono "Open Skin Library" > Import Skin (o al crear proyecto). Genera contenedores, botones con iconos PNG de la marca, textos, imagenes y acciones (mostrar/ocultar con fundido, siguiente/anterior, URL, JavaScript). Sobrevive al re-export y funciona con el VR de 3DVista. Use "plantilla" para una barra lista y/o "componentes" para un diseno a medida.

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": {
      "archivo_salida": "<archivo_salida>"
    },
    "name": "crear_skin_vts"
  }
}

Input Schema

NameRequiredDescriptionDefault
infoNo
temaNoVidrio oscuro (defecto) o claro
marcaNoIdentidad visual
tituloNoNombre del skin en 3DVista
botonesNoBotones de la barra, en orden (defecto anterior, siguiente, info, auto, opciones). "info" agrega Panel_Info; "opciones" agrega el menu plegable con los controles del visor.
fuentesNoFuentes propias a incrustar (.ttf/.otf). La primera familia se usa en todos los textos salvo marca.fuente. Sin esto se usa Montserrat incluida.
idiomasNoIdiomas del proyecto para los textos (defecto ["es","en"])
contactoNo
opcionesNoControles del menu plegable (defecto audio, pantalla, giroscopio, vr, hotspots). Usan los controles nativos de 3DVista; los de tipo interruptor cambian de icono segun el estado.
plantillaNoDefecto barra_inferior
componentesNoComponentes a medida (se suman a la plantilla). Cada uno: {tipo: contenedor|boton|boton_icono|texto|parrafo|imagen (texto = una linea; parrafo = texto largo con salto de linea), nombre, visible, posicion:{izquierda,derecha,arriba,abajo,ancho,alto} (numero=px o "50%"), disposicion: absoluta|horizontal|vertical, alineacion_h: izquierda|centro|derecha, alineacion_v: arriba|medio|abajo, separacion, relleno, fondo:{color,color2,opacidad,direccion}, radio, borde:{grosor,color}, sombra:{desenfoque,opacidad,distancia} o true, desenfoque (blur del fondo), texto, tamano_fuente, negrita, color_texto, fuente, tooltip, icono:{nombre, estilo, color, fondo, fondo_hover}, modo: push|toggle, icono_activo:{nombre, estilo, fondo, color} (estado activo del toggle), solo_si_giroscopio, tamano (boton_icono), imagen (ruta local), hijos:[...], acciones:[{tipo: mostrar|ocultar|alternar, componentes:[nombres], efecto} | {tipo: control, control: silencio|pantalla_completa|giroscopio|vr|hotspots|zoom_mas|zoom_menos|siguiente|anterior|pausa|reiniciar|mover_izquierda|mover_derecha|mover_arriba|mover_abajo} | {tipo: siguiente|anterior} | {tipo: url, url, nueva_pestana} | {tipo: javascript, codigo} | {tipo: codigo_mcp, accion, parametros} ]}
tamano_botonNopx (defecto 44)
auto_segundosNo
estilo_iconosNomoderno (defecto): iconos de linea finos con circulo de color al pasar el mouse
archivo_salidaYesRuta del .vts a crear
mostrar_nombreNoMostrar marca.nombre arriba a la izquierda (defecto true)
fuente_incluidaNoIncrustar Montserrat (incluida, licencia OFL) cuando no se pasan fuentes ni marca.fuente. Defecto true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A3.9/5.0
Behavior3/5

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

With zero annotations, the description carries the full behavioral burden, and it does add real value: the output survives re-export and works with 3DVista VR, which is non-obvious durability information. However, it never states what happens if archivo_salida already exists, that files are written to local disk, or what the tool reports back on success/failure — meaningful gaps for a file-generating mutation.

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?

The purpose comes first, then the generated content, then the import steps, then the parameter-selection hint — a clean front-loaded order. Every sentence carries distinct information; the import chain is the only borderline item, and it is short and actionable.

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 17-parameter, deeply nested generator with no output schema and no annotations, the description still covers the artifact type, the two construction modes, and the post-generation step. The remaining gap is what the tool returns and whether an existing .vts is overwritten, but the rich schema descriptions cover the parameters an agent needs to call it.

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 82%, so the baseline is 3; the description earns an extra point by explaining the intent behind key switches — 'plantilla' for a pre-built bar versus 'componentes' for a bespoke design — and by noting the PNG brand icons that the botones/marca parameters drive. It does not explain archivo_salida overwrite semantics or the fuentes/fuente_incluida interaction beyond what the schema already says.

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?

States a specific verb and artifact: 'Crea un skin NATIVO de 3DVista (.vts) listo para importar', and enumerates what it produces (contenedores, botones con iconos PNG, textos, imágenes, acciones). The capitalized 'NATIVO' plus the .vts extension implicitly separates it from the HTML-skin siblings, but no sibling is ever named, so the differentiation is inferred rather than stated.

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?

Explains the two usage modes directly — use 'plantilla' for a ready-made bar and/or 'componentes' for a custom design — and gives the concrete import path in 3DVista. It never says when NOT to use it or points to crear_skin_html / instalar_skin_html as alternatives, so an agent has context but no explicit routing away from this tool.

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