Skip to main content
Glama
Sign In
MCP 3DVista

MCP 3DVista

by juanchacon98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

instalar_skin_html

Reinstall a custom HTML skin into a 3DVista HTML5 export after re-exporting, copying the skin-3jc folder and injecting it so index.htm uses your skin again.

Instructions

Reinstala un skin HTML ya creado en un export (usar despues de re-exportar desde 3DVista, que reescribe index.htm). Copia la carpeta skin-3jc y la inyecta.

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": {
      "origen": "<origen>",
      "ruta_export": "<ruta_export>"
    },
    "name": "instalar_skin_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
origenYesCarpeta que contiene skin-3jc (o la propia skin-3jc)
ruta_exportYesCarpeta del export HTML5 de 3DVista (donde esta index.htm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on the 'why' (re-export overwrites index.htm) and the mechanism (copy skin-3jc folder, inject), but says nothing about whether an existing skin folder in the export is overwritten, whether a backup is made, or what happens if index.htm is missing.

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 short sentences, front-loaded with the action and followed by the condition and the mechanism. Nothing is redundant and the parenthetical rationale is the single most useful piece of context.

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

Completeness3/5

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

For a two-parameter mutation with no annotations and no output schema, the description covers purpose, trigger, and mechanism but omits overwrite/backup semantics and any indication of success or failure behavior. Adequate to call correctly, thin on consequences.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema itself (origen contains skin-3jc or is skin-3jc; ruta_export is where index.htm lives). The description adds no syntax, path format, or edge-case meaning beyond that, so the baseline 3 applies.

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 resource: reinstall an already-created HTML skin into an export. The mechanics are concrete ('Copia la carpeta skin-3jc y la inyecta'), and 'ya creado' implicitly distinguishes it from crear_skin_html, though no sibling is named explicitly.

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?

Gives a clear triggering condition: use it after re-exporting from 3DVista, because that export rewrites index.htm and wipes the injection. It lacks an explicit counter-case (e.g. 'use crear_skin_html if no skin exists yet'), but the timing guidance is decision-useful.

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