Skip to main content
Glama

tia_tecnologia

Create and configure Siemens PID_Compact technology objects in TIA Portal projects: list types, set names/versions, inspect parameters, and write PID values.

Instructions

Objetos tecnológicos (regulación PID).

  • tipos: tipos habituales en S7-1200 y para qué sirven.

  • listar | crear: nombre + tipo ('PID_Compact') + version (según firmware de la CPU, p. ej. '2.3').

  • parametros: nombre [+ filtro] → parámetros y valores (límites, escalado, ganancias...).

  • escribir_parametro: nombre + parametro + valor (muestra valor anterior → nuevo). Flujo PID típico: crear el objeto → OB de alarma cíclica (OB30) que llame a PID_Compact (en SCL con tia_programar/importar_scl o en KOP con la caja PID_COMPACT) → configurar parámetros.

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

Input Schema

NameRequiredDescriptionDefault
plcNo
tipoNo
valorNo
actionYes
filtroNo
nombreNo
versionNo
parametroNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavior context beyond that: 'escribir_parametro' reports the previous value alongside the new one, and 'version' must match the CPU firmware (e.g. '2.3'). It does not say whether writes persist to the project, require an online connection, or are reversible, which would matter for a mixed read/write tool.

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?

Structure is excellent for a multi-action tool: scope first, then one bullet per action, then a workflow line. Dense but every line carries information; only 'tipos' is left slightly vague ('tipos habituales en S7-1200 y para qué sirven').

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?

An output schema exists, so return values need no explanation, and the description covers the action set, per-action parameter pairing and the end-to-end PID workflow. The unexplained 'plc' parameter and the absence of any online/offline or state requirement keep it short of full completeness for an 8-parameter mixed-mode tool.

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% across 8 parameters, so the description carries the full burden and does most of it well: it specifies which parameters pair with which action (nombre+tipo+version for crear, nombre/filtro for parametros, nombre+parametro+valor for escribir_parametro) and gives example values for tipo and version. The 'plc' parameter is never mentioned, leaving a real gap.

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?

The opening line names the resource ('Objetos tecnológicos') and its domain (PID regulation), then each bullet maps an action enum value (tipos, listar, crear, parametros, escribir_parametro) to the specific operation it performs. An agent can tell this is a multi-action tool for TIA Portal technology objects, distinct from siblings like tia_programar or tia_tags, though it never explicitly contrasts itself with them.

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?

The 'Flujo PID típico' section gives an explicit ordered workflow (create the object → cyclic alarm OB30 calling PID_Compact → configure parameters) and names the alternatives for implementing the call (tia_programar/importar_scl in SCL vs. the PID_COMPACT box in KOP). What is missing is when-not guidance, e.g. when to use 'parametros' versus 'escribir_parametro' for inspection vs. modification.

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