Skip to main content
Glama

tia_compilar

Read-only

Compiles TIA Portal PLC software or a specified block, returning errors and warnings with block and network locations to help locate and fix issues.

Instructions

Compilar y obtener errores/advertencias con su ubicación (bloque › red).

  • software: todo el programa del PLC (la primera vez puede tardar 30-60 s).

  • bloque: solo nombre.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tia_compilar"
  }
}

Input Schema

NameRequiredDescriptionDefault
plcNo
actionNosoftware
nombreNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: first-run compile of the whole program can take 30-60 s, which matters for timeout and retry planning. It does not state what happens to existing compiled artifacts or whether a failed compile blocks subsequent operations.

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 verb and the return value, then two tight bullets with no filler. Nothing is wasted, though the fragment "bloque: solo `nombre`" is terse to the point of being slightly cryptic about the required dependency.

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 described. However, with three undocumented parameters and a mode-dependent required field, the definition leaves the agent to infer the role of `plc` and the action-nombre dependency. Adequate for a simple two-mode compile call, but not fully self-contained.

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 all parameter meaning, and it only partially does: it explains the `action` values and that `nombre` applies to the `bloque` mode. The `plc` parameter is never mentioned, and it is not stated that `nombre` is effectively required when action=bloque.

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?

A specific verb plus resource: "Compilar" applied to the PLC program, with the explicit payoff of returning errors/warnings located by block › network. It also names the two compile scopes (whole software vs. a single block), which separates the two modes. It stops short of naming which sibling to use instead for related analysis tasks, so it is clear but not sibling-differentiated.

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 two bullets define exactly what each `action` value does and when to pick it: `software` for the entire PLC program, `bloque` for a single block identified by `nombre`. The 30-60 s first-run warning tells the agent when this call is slow. There are no explicit exclusions or named alternative tools, so it lands at 4 rather than 5.

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