Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

crear_iconos_svg

Generates brand-colored SVG icons, hover variants, and optional PNGs for 3DVista Skin Editor Icon Buttons.

Instructions

Genera un set de iconos SVG con los colores de la marca para usar en Icon Buttons del Skin Editor (incluye variante _activo para hover). Iconos: menu, cerrar, escenas, info, pantalla, pantalla_salir, audio, audio_off, compartir, whatsapp, telefono, correo, inicio, mapa, ubicacion, anterior, siguiente, arriba, abajo, play, pausa, buscar, idioma, vr, giroscopio, camara, hotspot, hotspot_off, ajustes, zoom_mas, zoom_menos, vr_off, mas, enlace, descargar, calendario, usuario

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": {
      "carpeta_salida": "<carpeta_salida>"
    },
    "name": "crear_iconos_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
pngNoGenerar tambien PNG (defecto true; 3DVista no muestra SVG en Icon Buttons)
colorNoColor del trazo (defecto #ffffff)
fondoNoColor de fondo para circulo/cuadrado
estiloNo
grosorNoGrosor del trazo (defecto 2)
iconosNoVacio = todos
tamanoNopx (defecto 128)
prefijoNo
carpeta_salidaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add real behavior (hover variant '_activo' is auto-generated, brand-colored output, a fixed inventory of 37 icons). However, for a tool that writes files it never states that files are written into carpeta_salida, whether existing files are overwritten, what the return value is, or that PNG output is on by default (that fact only survives in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is well front-loaded and dense with useful detail, but the enumerated roster of 37 icon names is duplicated from the schema enum and bloats the definition without adding information. Trimming the roster would leave a tight, well-structured definition.

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?

A 9-parameter, file-emitting tool with zero annotations and no output schema needs more than this: file naming/prefijo behavior, overwrite semantics, default PNG behavior and return shape are all absent. The description explains what icons exist but not what an agent can expect after the call.

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

Parameters2/5

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

At 67% schema coverage the description should compensate, but it mostly restates the 'iconos' enum verbatim — information the schema already provides — while prefijo has no description anywhere and the required carpeta_salida target is never explained. Nothing is said about estilo/grosor/tamano/fondo semantics beyond what the schema already documents.

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 concrete verb+resource ('Genera un set de iconos SVG') plus destination context ('Icon Buttons del Skin Editor') and the hover-variant detail, so the agent knows exactly what artifact is produced. It never names a sibling or explicitly says it is the icon-producing counterpart to crear_skin_html/crear_skin_vts, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent must infer that this tool is the one to call when a skin needs Icon Button assets. There is no when-to-use clause, no prerequisites (e.g. that a skin project must exist first), and no named alternative to avoid.

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