Skip to main content
Glama
MCP 3DVista

MCP 3DVista

by juanchacon98

instalar_ayudante

Installs the window.TDVH helper into a 3DVista HTML5 export so you can run helper-mode code and debug from the browser console with TDVH.diagnostico().

Instructions

Instala solo el ayudante window.TDVH en el export para poder usar codigo en modo "helper" y depurar desde la consola (TDVH.diagnostico()).

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": "instalar_ayudante"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.4/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 whole behavioral burden. It does disclose the key side effect (a window.TDVH global is added to the export) and the payoff (TDVH.diagnostico() from the console), which is meaningful context. It stops short of saying whether existing export files are modified or overwritten, whether the change is reversible, or whether the export must be closed/validated first.

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?

A single front-loaded sentence that states the target artifact first and the motivation second, with no filler. Minor friction from the nested quoted "helper" and the parenthetical call example, but nothing that wastes the reader's time.

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 one-parameter tool with no output schema and no annotations, the description covers what is installed and why, which is close to sufficient. The remaining gap is that an agent cannot tell what happens if the helper is already present, or how the install is undone, which matters because several siblings (quitar_inyeccion, inyectar_en_export) operate on the same export.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description refers to "el export", which aligns with the schema's "Carpeta del export HTML5 de 3DVista (donde esta index.htm)" but adds no new syntax, constraints, or failure modes beyond what the schema already states.

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?

"Instala solo el ayudante window.TDVH en el export" gives a specific verb (instala) and a specific artifact (the window.TDVH helper), and the word "solo" implicitly distinguishes it from tools that install more than the helper. An agent can tell this is a narrow single-artifact install rather than a full injection, though the sibling it contrasts with (inyectar_en_export) is never named.

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?

The purpose clause ("para poder usar codigo en modo helper y depurar desde la consola") implies the situation in which to reach for this tool: you want console-based debugging in an export. However, it states no when-not conditions, no prerequisites, and no comparison against the obvious alternative of a full injection, so an agent must infer the selection criteria.

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