Skip to main content
Glama

tia_red

Configures offline PROFINET/Ethernet settings in TIA Portal projects, including device IPs, PROFINET names, subnets, IO systems, modules, and IO address ranges without touching real equipment.

Instructions

Red PROFINET/Ethernet del proyecto (configuración OFFLINE; no toca equipos reales).

  • interfaces: IP, máscara, nombre PROFINET, subred, sistema IO y rol de cada equipo.

  • configurar: dispositivo + ip / mascara / nombre_profinet (minúsculas, p. ej. 'servo-eje-x').

  • subred: conecta dispositivo a subred (la crea si no existe; por defecto PN/IE_1).

  • asignar_plc: conecta dispositivo (drive, lector DMC, ET 200...) al sistema IO de plc_destino.

  • agregar_dispositivo: dispositivo (nombre) + identificador: referencia de catálogo ('6SL3210-5FE10-4UF0/V1.0') o GSDML instalado ('GSD:GSDML-V2.35-...xml/DAP/DAP 1').

  • insertar_modulo: dispositivo + identificador + modulo (nombre) + posicion [+ contenedor] (p. ej. telegrama de un drive o módulo de una ET 200).

  • direcciones_io: rangos %I/%Q de cada módulo de dispositivo.

  • cambiar_direccion_io: dispositivo + modulo + tipo_io + inicio (byte).

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

Input Schema

NameRequiredDescriptionDefault
ipNo
actionYes
inicioNo
moduloNo
subredNoPN/IE_1
mascaraNo
tipo_ioNo
posicionNo
contenedorNo
dispositivoNo
plc_destinoNo
identificadorNo
nombre_profinetNo

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 already declare it as mutating but non-destructive and closed-world; the description adds the key extra fact that changes affect only project configuration and never real hardware, which explains the openWorldHint=false profile in operational terms. It also discloses the side effect that `subred` creates the subnet when it does not exist, though it says nothing about persistence (saving the project) or permission requirements.

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 with the one-sentence scope statement, then a tightly formatted bullet per action with parameters in backticks. Density is justified by eight distinct actions, and there is little filler, though a few bullets (contenedor, posicion) read as fragments rather than complete explanations.

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 an eight-action, 13-parameter configuration tool the coverage is good: scope, per-action parameter mapping, an example identifier format, and units are all present, and the existence of an output schema means return values need not be described. Missing pieces are minor but real — no statement of prerequisites (project/session state) and no guidance on whether changes persist automatically.

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?

With 0% schema description coverage, the description carries the whole burden and mostly delivers: it maps every one of the 13 parameters to an action and adds real semantics such as lowercase PROFINET name formatting ('servo-eje-x'), catalog/GSDML reference examples for `identificador`, byte units for `inicio`, and the PN/IE_1 default for `subred`. A few remain thin — `posicion` and `contenedor` are only named, and the Input/Output values of `tipo_io` are not restated.

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?

Opens with a specific verb+resource (network configuration of PROFINET/Ethernet in the project) and immediately scopes it as OFFLINE configuration that does not touch real equipment, which separates it from anything that would act on live devices. The bullet list then names the concrete operation each action performs, so an agent knows the tool's scope without opening the schema.

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 OFFLINE / no-real-hardware scope plus the per-action bullets give strong implicit guidance on which action to pick for a given task (e.g. agregar_dispositivo vs insertar_modulo are clearly separated). However, nothing tells the agent when to prefer this tool over siblings such as tia_hardware or tia_proyecto, and no prerequisites (open project/session) are stated.

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