Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

planificar_skin_nativo

Generates a 3DVista native skin plan, including component tree, sizes, colors, and action code, to guide Skin Editor setup for modules like bar, scenes, logo, info, languages, and welcome.

Instructions

Produce el plano de un skin para el Skin Editor de 3DVista: arbol de componentes con nombres, tamanos, colores y el codigo de cada accion. Modulos: barra, escenas, logo, info, titulo_escena, whatsapp_flotante, idiomas, bienvenida

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "planificar_skin_nativo"
  }
}

Input Schema

NameRequiredDescriptionDefault
marcaNoIdentidad visual
idiomasNo
modulosNo
contactoNo
guardar_enNoRuta .md opcional para guardar el plan
auto_segundosNo

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 at all, the description carries the full burden. It does add real behavioral context by clarifying the output is a plan/blueprint (component tree, sizes, colors, per-action code) rather than an installed skin, but it never states whether anything is written to disk, what permissions are needed, or how the returned plan is delivered — the save-to-.md behavior only surfaces 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.

Conciseness5/5

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

Two tight sentences: the first front-loads the artifact and its contents, the second enumerates the supported modules. No filler, no restating of the name.

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?

For a 6-parameter tool with nested objects, zero annotations and no output schema, the description leaves too much open: the meaning of contacto and auto_segundos, whether a file is persisted, and the relationship to the crear_skin_* siblings are all unaddressed.

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?

Schema description coverage is only 33% on 6 top-level parameters including two nested objects, so the description needs to compensate. It only echoes the 'modulos' list (already an enum in the schema) and alludes to names/colors/sizes; marca's identity fields, idiomas, contacto (whatsapp, ubicacion_url, incluir_escena), auto_segundos and guardar_en get no explanation.

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: 'Produce el plano de un skin' for the 3DVista Skin Editor, and enumerates what the plan contains (component tree with names, sizes, colors, action code) plus the modules it supports. An agent can tell this generates a blueprint rather than an installable skin, which implicitly separates it from crear_skin_html/crear_skin_vts, though no sibling is named.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The verb 'produce el plano' hints at a planning step before creating a skin, but the agent must infer that distinction from sibling names rather than from the description.

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