Skip to main content
Glama

tia_bloques

Read-only

Lists, reads, and exports Siemens TIA Portal PLC blocks as source, XML, or text so you can inspect logic, copy formats, and version projects in Git.

Instructions

Leer el programa del PLC (plc opcional si hay uno solo).

  • listar: bloques con tipo, número, lenguaje, consistencia y carpeta (filtro por texto).

  • leer: nombre → KOP/FUP como lógica en texto + interfaz; SCL/STL/DB como fuente.

  • xml: SimaticML crudo del bloque nombre (para copiar formato o editar a mano).

  • fuente: fuente SCL/STL/DB generada por TIA.

  • exportar_todo: XML + .scl + .txt + UDT + tags a carpeta (para versionar en Git) y perfil de estilo.

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

Input Schema

NameRequiredDescriptionDefault
plcNo
actionYes
filtroNo
limiteNo
nombreNo
carpetaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description only needs to add what they cannot. It does add useful scope (optional `plc` when only one project is open, the extra style profile emitted by exportar_todo), but it never says whether exportar_todo overwrites existing files or requires filesystem write permissions — a real side effect that sits in mild tension with readOnlyHint=true.

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?

One scoping sentence followed by five bullets, one per enum value, in the same order as the action enum. No filler, no repetition of the schema, and the reader can scan directly to the action they need.

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-value documentation is correctly omitted. However, for a six-parameter tool the description leaves `limite` undocumented and does not state which optional parameters become required per action (nombre for leer/xml/fuente, carpeta for exportar_todo), which are the two failure modes an agent is most likely to hit.

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 has to carry all parameter meaning, and it mostly does: `plc` (optional if there is only one), `filtro` (text filter for listar), `nombre` (block for leer/xml/fuente), `carpeta` (destination for exportar_todo). `limite` (default 200) is never mentioned, and it is unclear whether `nombre` or `carpeta` are mandatory for their respective actions.

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?

The opening line names the resource (PLC program blocks) and the description then enumerates each action with its concrete output: 'listar' returns type/number/language/consistency/folder, 'leer' returns KOP/FUP as text logic or SCL/STL/DB source, 'xml' returns raw SimaticML, 'exportar_todo' writes XML + .scl + .txt + UDT + tags to a folder. An agent knows exactly what it will get for each action 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 Guidelines4/5

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

Each action carries an implicit use case — 'xml' is flagged 'para copiar formato o editar a mano' and 'exportar_todo' is flagged 'para versionar en Git' — which effectively tells the agent which action maps to which intent. What is missing is explicit routing against siblings (e.g. tia_udt or tia_tags for UDT/tag-only work) and any statement of when not to use this tool.

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