Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

analizar_tour

Read a 3DVista HTML5 export to list scenes, exact skin component names, hotspots, languages, and script functions before generating code that relies on those names.

Instructions

Lee un export HTML5 de 3DVista y lista escenas (en orden), componentes del skin con sus nombres exactos, hotspots, idiomas y funciones de script disponibles. Usar SIEMPRE antes de generar codigo que dependa de nombres.

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_export": "<ruta_export>"
    },
    "name": "analizar_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtroNoTexto para filtrar escenas/componentes/hotspots
idiomaNoCodigo de idioma para las etiquetas (es, en…)
formatoNo
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

A4/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 behavioral burden. 'Lee' and 'lista' imply a non-mutating inspection, but it never confirms that nothing is written to the export, how it behaves on a folder lacking index.htm, or how large exports are handled. The enumeration of returned artifacts is the main behavioral value added.

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 dense sentences, no filler, with the purpose stated first and the mandatory usage rule second. Every phrase contributes something an agent can act on.

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?

With no output schema, the description compensates well by enumerating the returned artifacts (scenes, components, hotspots, languages, script functions). It falls slightly short of fully covering a no-annotation tool, since failure modes and the effect of formato on the result are left unstated.

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 coverage is 75%, so most parameters are already documented in the schema. The description adds only indirect meaning: 'idiomas' hints at the idioma parameter and the listed artifacts hint at filtro, but ruta_export and formato get no elaboration beyond what the schema states. Baseline 3 is appropriate.

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?

Names a specific verb and resource ('Lee un export HTML5 de 3DVista') and then enumerates exactly what it returns: scenes in order, skin components with exact names, hotspots, languages and script functions. That level of detail distinguishes it from read-only siblings like leer_skin_vts, which would only cover the skin file.

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 an explicit, emphatic trigger: 'Usar SIEMPRE antes de generar codigo que dependa de nombres', which effectively routes the agent away from generar_codigo until this has run. It stops short of stating when NOT to use it, or naming a lighter alternative for exports that need no name resolution.

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