Skip to main content
Glama

tia_proyecto

Manage Siemens TIA Portal V17 project copies: inspect project details, open read-only, create, unarchive, save, close, or archive files within permitted folders.

Instructions

Proyecto TIA (solo COPIAS dentro de las rutas permitidas).

  • info: nombre, ruta, idioma de edición, si tiene cambios sin guardar.

  • abrir: ruta al .ap17 (solo_lectura=true para solo consultar).

  • crear: carpeta + nombre (sin acentos ni espacios).

  • desarchivar: ruta al .zap17 (puede estar en cualquier lado) → copia en carpeta permitida.

  • guardar | cerrar (guardar_cambios) | archivar: carpeta + nombre → crea .zap17.

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

Input Schema

NameRequiredDescriptionDefault
rutaNo
actionYes
nombreNo
carpetaNo
solo_lecturaNo
guardar_cambiosNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.3/5.0
Behavior4/5

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

The header 'solo COPIAS dentro de las rutas permitidas' is a genuine operational constraint that annotations do not express, and the desarchivar line clarifies the source .zap17 may live anywhere but the copy lands only in a permitted `carpeta`. Annotations already cover the readOnly/destructive/openWorld profile, so this added scoping context is what earns the score. It stops short of saying whether guardar/archivar overwrite an existing <nombre>.zap17.

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?

A one-line scope statement followed by a bullet per action, front-loading the most important constraint (copies only, permitted paths). No filler sentences; every line carries either a parameter mapping or a behavioral rule.

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 a six-parameter, seven-action tool this covers the action-to-parameter mapping, the copy-only constraint, and the naming rule, and an output schema exists so return values need no explanation. What is missing is failure behavior and whether an existing archive with the same name is replaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 meaning and it does: it maps every one of the six parameters to the actions that use them and explains the action enum value by value. It also adds a naming constraint not present in the schema ('sin acentos ni espacios') and the resulting file name convention (<nombre>.zap17).

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?

The description names the resource (Proyecto TIA) and enumerates seven concrete actions (info, abrir, crear, desarchivar, guardar, cerrar, archivar), each with a specific verb-object meaning. An agent can tell what each action does without opening the schema. It does not explicitly distinguish this tool from siblings such as tia_sesion or tia_compilar, which keeps it below a 5.

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 line states the parameters that select it (`ruta` for abrir/desarchivar, `carpeta`+`nombre` for crear/guardar/cerrar/archivar) and gives a conditional rule: `solo_lectura`=true when only consulting. That is clear per-action usage guidance. It offers no when-not-to-use guidance or explicit routing to alternative tools.

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