Skip to main content
Glama

tia_sesion

Connect to and manage Siemens TIA Portal V17 sessions by checking status, attaching to or starting an instance, and disconnecting when done.

Instructions

Conexión con TIA Portal V17. EMPIEZA AQUÍ.

  • estado: procesos de TIA abiertos, conexión, proyecto activo y rutas permitidas.

  • conectar: se adjunta al TIA abierto (o al pid indicado); si no hay, inicia TIA (con_interfaz=false lo abre oculto, más rápido). nueva_instancia=true inicia un TIA propio aunque el usuario tenga otro abierto (recomendado si el usuario está trabajando en TIA). La 1.ª vez TIA pide autorizar Openness: el usuario debe responder "Sí a todo" en TIA.

  • desconectar: suelta TIA (si lo inició el servidor, lo cierra).

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

Input Schema

NameRequiredDescriptionDefault
pidNo
actionYes
con_interfazNo
nueva_instanciaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the tool is not read-only, not destructive and not open-world; the description adds real behavioral context on top: it may launch TIA, `desconectar` closes TIA only if the server started it, and the first run triggers an Openness authorization prompt the user must answer. These side effects and the interactive prerequisite are exactly what an agent needs and are not inferable from annotations or schema.

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 identity plus a routing cue, then a tight bullet per action with no filler. A few clauses are dense but every sentence carries operational information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a session-lifecycle tool with an output schema and annotations already covering the safety profile, the description covers all three actions, their side effects, and the first-run permission caveat. Nothing an agent needs in order to invoke it correctly appears to be missing.

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 carries the load, and it does explain `con_interfaz` (hidden/faster), `nueva_instancia` (own TIA instance, recommended when the user is active) and the three `action` values. `pid` is only referenced in passing ('o al `pid` indicado') without saying which process id it is or how to obtain it, leaving one 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?

Names a concrete resource and scope ('Conexión con TIA Portal V17') and marks itself as the entry point ('EMPIEZA AQUÍ'), which tells an agent this is the prerequisite session tool rather than one of the tia_* work tools. It stops short of explicitly contrasting its scope with named siblings, so it is clear but not maximally differentiating.

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 action bullets give conditional guidance: use 'conectar' to attach to a running TIA or pass `pid`; use `con_interfaz`=false for a faster hidden launch; use `nueva_instancia`=true when the user is already working in TIA. It does not state when to avoid an action (e.g., connecting while another session is held), so it is strong but not fully exclusive.

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