Skip to main content
Glama

tia_udt

Create, list, read, or delete Siemens TIA Portal V17 user-defined data types (UDTs) via SCL, enabling reusable PLC data structures for interfaces and tags.

Instructions

Tipos de datos de usuario (UDT / PLC data types).

  • listar | leer: nombre → estructura con tipos, valores iniciales y comentarios.

  • crear: codigo SCL, p. ej. TYPE "UDT_Motor" VERSION : 0.1 STRUCT Marcha : Bool; ... END_STRUCT; END_TYPE (varios TYPE en un mismo código; también sirve para modificar uno existente).

  • borrar: nombre. Para usar un UDT en una interfaz o tag, escribe el tipo entre comillas: "UDT_Motor".

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_udt"
  }
}

Input Schema

NameRequiredDescriptionDefault
plcNo
actionYes
codigoNo
nombreNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

B3/5.0
Behavior1/5

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

The description discloses a `borrar` action that removes a UDT by name, which is a destructive mutation, while the annotations declare destructiveHint=false and readOnlyHint=false. That is a direct conflict between the stated behavior and the supplied annotations. The description also adds nothing about whether crear silently overwrites/modifies an existing type (it explicitly says it can modify one) or what happens on name collisions.

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?

Front-loaded one-line purpose followed by action-keyed bullets, which is easy to scan. The SCL snippet is truncated with "..." and slightly verbose, but every bullet maps to a real action, so little is wasted.

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?

An output schema exists, so return values need not be explained, and the description covers the create/read/delete paths plus the interface-quoting convention. It is still incomplete for a mutation-capable tool: the `plc` scoping parameter is undocumented and there is no mention of permission requirements, reference/dependency checks before deletion, or whether crear overwrites an existing type silently.

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 0%, so the description must carry the burden. It does well for `codigo`, giving an SCL TYPE example, noting multiple TYPE blocks per code and that it doubles as an edit path, and it maps `nombre` to the read/delete actions; `action` is covered by the bullet list. But `plc` is never mentioned anywhere, leaving one of four parameters entirely undefined.

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 the resource precisely ("Tipos de datos de usuario (UDT / PLC data types)") and enumerates the four actions performed on it, so an agent knows exactly which object family it is dealing with. It does not distinguish itself from siblings such as tia_tags or tia_bloques, which is a gap, but the verb+resource is unambiguous.

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 per-action bullets give implicit guidance (name for listar/leer/borrar, SCL code for crear), and the note about quoting the type name in interfaces is a genuinely useful usage rule. However there is no explicit statement of when to reach for this tool over tag or block tools, no prerequisites, and no warning about deleting a UDT that is still referenced.

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