Skip to main content
Glama

tia_conocimiento

Learns team coding conventions from prior TIA Portal V17 project copies, lists learned projects, and returns style profiles to follow before programming.

Instructions

Aprender el estilo del equipo a partir de proyectos V17 anteriores (copias).

  • aprender: ruta a un .ap17 (en carpeta permitida) o .zap17 (se desarchiva en una copia). Se abre en solo lectura, se exporta todo y se genera PERFIL_ESTILO.md (prefijos, estructura, comentarios, instrucciones usadas, árbol de llamadas y redes de ejemplo). No se guarda nada en el proyecto.

  • listar: proyectos ya aprendidos.

  • perfil: nombre → PERFIL_ESTILO.md. LÉELO antes de programar para seguir las convenciones del equipo.

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

Input Schema

NameRequiredDescriptionDefault
rutaNo
actionYes
nombreNo
carpeta_desarchivadoNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, but the description adds important behavior the agent could not infer: the project is opened read-only, nothing is saved into the project, and a .zap17 is unarchived into a copy. That covers side effects and safety well. It leaves open where PERFIL_ESTILO.md is written and how expensive learning a large project is.

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?

The bullet-per-action layout is front-loaded and maps one-to-one onto the `action` enum, so the agent can scan directly to the mode it needs. Each sentence carries new information; only the emphasis markers and minor phrasing keep it from being maximally tight.

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 multi-action tool with an output schema (so return values need not be explained), the definition covers purpose, each mode's mechanics, safety characteristics and the post-condition of reading the generated profile before programming. The residual gap around `carpeta_desarchivado` is minor relative to the overall completeness.

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 parameter meaning, and it does explain `ruta` (path to a .ap17/.zap17, permitted folder) and `nombre` (target for the perfil action). However, `carpeta_desarchivado` is never addressed beyond the incidental phrase 'se desarchiva en una copia', leaving one of four parameters semantically uncovered.

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 headline states a specific verb+resource: 'Aprender el estilo del equipo a partir de proyectos V17 anteriores (copias)', and the bullets define three distinct operations (aprender/listar/perfil) with concrete artifacts (PERFIL_ESTILO.md). It is unambiguous what the tool produces. It does not explicitly contrast itself with the many tia_* siblings, which is the only thing keeping it from 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?

The definition gives clear operational context per action: aprender takes a `ruta` to .ap17/.zap17 inside a permitted folder, and perfil carries an explicit instruction ('LÉELO antes de programar para seguir las convenciones del equipo') that tells the agent when the output matters. There are no explicit exclusions or named alternative tools, so it stops short of full when/when-not guidance.

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