Skip to main content
Glama

tia_hardware

Read-only

List project devices or add a PLC by name and reference/firmware to manage Siemens TIA Portal V17 hardware configuration.

Instructions

Dispositivos del proyecto.

  • dispositivos: cada equipo con sus módulos (referencia/firmware, posición, IP) y su PLC.

  • agregar_plc: nombre + referencia con firmware, p. ej. '6ES7 214-1BG40-0XB0/V4.5' (S7-1214C AC/DC/RLY).

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

Input Schema

NameRequiredDescriptionDefault
actionYes
nombreNo
referenciaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

C2.3/5.0
Behavior1/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description advertises an "agregar_plc" action that adds a device to the project — an inherently mutating operation. That is a direct inconsistency an agent could act on incorrectly, and no permissions, side effects, or duplicate-handling behavior are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A headline plus two short bullets is efficiently sized with no filler, but the brevity comes at the cost of under-specification and the heading is not information-bearing. The action-to-parameter mapping is only implied by bullet position rather than stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a tool that includes a write action with zero annotation support and 0% parameter coverage the description leaves too much out. It omits prerequisites, duplicate/existing-PLC behavior, and the meaning of `nombre`, which an agent needs in order to call agregar_plc correctly.

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 parameter load. It does add real value for `referencia` by giving the firmware format and a concrete example ('6ES7 214-1BG40-0XB0/V4.5', S7-1214C AC/DC/RLY), but `nombre` is left unexplained (display name? uniqueness?) and nothing says that `dispositivos` takes no extra parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The top-level statement "Dispositivos del proyecto" is a vague noun phrase that does not name a verb or the two distinct operations the tool performs. The bullets do clarify the concrete actions (list devices with modules/PLC, add a PLC with nombre + referencia), but the agent must parse the child bullets to learn the purpose, and the tool name alone (tia_hardware) does not disambiguate it from siblings like tia_red or tia_hmi.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use "dispositivos" versus "agregar_plc", nor when to reach for this tool instead of tia_red (network/IPs) or tia_proyecto. There is no mention of prerequisites such as whether a project must be open or a session established before llamar a agregar_plc, leaving routing and sequencing entirely to inference.

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