Skip to main content
Glama

tia_hmi

Create, inspect, and compile WinCC HMI panels, screens, tags, and text lists in TIA Portal, with PLC connection setup, XML import/export, and screen previews.

Instructions

Paneles HMI WinCC Basic/Comfort (p. ej. KTP400 Basic). panel opcional si hay uno solo.

  • paneles: paneles con sus pantallas, plantillas, tablas de tags y listas de textos.

  • agregar_panel: nombre + referencia con versión ('6AV2 123-2DB03-0AX0/17.0.0.0' = KTP400 Basic).

  • conectar_plc: panel + plc a la misma subred (+ instrucciones para la conexión HMI, que es manual).

  • leer: tipo (pantalla|plantilla|tags|lista_textos) + nombre → resumen legible (objetos, posición, colores, eventos, animaciones, tags). Úsalo para aprender diseños de proyectos anteriores.

  • xml: SimaticML crudo de ese objeto.

  • crear_pantalla: especificacion JSON (ver action='ayuda'); reemplaza si ya existe.

  • crear_tags: nombre (tabla) + tags. Si algún tag usa conexion, pasa conexion_confirmada=true SOLO si esa conexión HMI ya existe: importar tags con una conexión inexistente CIERRA TIA. crear_lista_textos: nombre + entradas.

  • importar_xml: tipo + xml (SimaticML HMI completo).

  • compilar: compila el panel y devuelve errores/advertencias.

  • exportar: todo el panel a carpeta (XML).

  • vista_previa: PNG de una pantalla en carpeta: desde especificacion (sin TIA) o desde la pantalla nombre del panel. Úsalo para revisar el diseño y para enseñárselo al usuario.

  • ayuda: formato de las especificaciones.

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": {
      "action": "<action>"
    },
    "name": "tia_hmi"
  }
}

Input Schema

NameRequiredDescriptionDefault
plcNo
xmlNo
tagsNo
tipoNo
panelNo
actionYes
nombreNo
carpetaNo
entradasNo
referenciaNo
especificacionNo
conexion_confirmadaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only give the generic readOnly=false/destructive=false/openWorld=false profile, while the description adds high-value behavior: `crear_pantalla` replaces an existing screen, tag import against a nonexistent connection crashes TIA, and the HMI-PLC connection step is manual. That is real operational risk disclosure the agent could not infer elsewhere. Minor tension: overwriting an existing screen is arguably a destructive update even though destructiveHint=false, though this reads as an annotation imprecision rather than a contradiction of intent.

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?

A one-line scope header followed by one bullet per action, with parameter names in backticks and warnings placed inline where they matter. Given 13 actions it is compact and front-loaded, with no filler sentences. The only blemish is `crear_lista_textos` being folded into the `crear_tags` bullet.

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?

For a 13-action, 12-parameter mutation tool this covers the dispatch surface well, and with an output schema present it need not explain return values. Still, a few call-critical details are left to the `ayuda` action (specification format, tag/entry object shapes) and the 'conexion' tipo value is undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does most of it: it defines `panel` optionality, `referencia` with a concrete version string example, `nombre` per action (panel name, tag table, text list), `plc`, `xml`, `especificacion` (deferring details to action='ayuda'), `carpeta`, and the `conexion_confirmada` precondition. Gaps remain: `entradas` and `tags` shapes are never described, and the `tipo` enum used in the description omits the schema's 'conexion' value.

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?

Each of the 13 `action` values is enumerated with a concrete verb+resource: 'paneles' lists panels and their contents, 'crear_pantalla' creates screens, 'compilar' compiles and returns errors/warnings, 'exportar' dumps the whole panel to a folder. The HMI-panel scope is unmistakable and distinct from the other tia_* domains (bloques, tags, red). It never explicitly contrasts itself with a sibling, so a 4 rather than a 5.

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?

Several actions carry explicit usage guidance: 'leer' is for learning designs from previous projects, 'vista_previa' is for reviewing the design and showing it to the user, 'ayuda' explains the specification format, and `panel` is declared optional when there is only one. The safety rule for `conexion_confirmada` is spelled out with a precondition. What is missing is any when-not-to-use or routing to sibling tools (e.g. HMI tag tables vs tia_tags).

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