Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

leer_skin_vts

Reads a .vts skin file and returns its component tree with names, actions, and text so you can inspect an existing or generated 3DVista skin.

Instructions

Lee un skin .vts (exportado con "Save Skin as Portable File" o de la biblioteca de 3DVista) y muestra su arbol de componentes, nombres, acciones y textos. Util para aprender de un skin existente o revisar uno generado.

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": {
      "ruta": "<ruta>"
    },
    "name": "leer_skin_vts"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutaYes
formatoNo

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?

With no annotations, the description carries the full burden; "Lee" and "muestra" imply a non-mutating read and it usefully describes what is returned (tree, names, actions, texts). However it does not explicitly declare read-only safety or explain what the formato parameter changes, leaving gaps for a tool with zero annotation coverage.

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?

Two tight sentences front-loaded with verb and resource, zero filler. The structure is clean, though the second sentence could also have covered the formato output modes rather than only motivation.

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 read-only tool with no output schema and an undocumented enum, the description covers purpose and return content but leaves the output format choice (resumen/json) unexplained. An agent can call it but cannot predict what each formato value yields.

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 coverage is 0% and neither parameter is described in the schema. The description implies ruta is the .vts file path but adds no format/syntax detail, and it never explains the formato enum (resumen vs json), so it fails to compensate for the documentation gap on 2 parameters.

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?

States a specific verb (Lee) and resource (.vts skin) plus what it exposes: the component tree, names, actions, and texts. It also names the export mechanism ("Save Skin as Portable File" or the 3DVista library), letting an agent distinguish it from the crear_skin_vts/crear_skin_html siblings that write skins.

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?

"Util para aprender de un skin existente o revisar uno generado" gives clear when-to-use context. It stops short of explicitly recommending the crear_* siblings for the write path or stating when not to use it, so it is a 4 rather than a 5.

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