Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Importar Empleados a SIIGO

siigo_pushempl
Destructive

Import employee records from an Excel (.xlsx) file into SIIGO Pyme. Configure company, year, and accounting norm; errors are logged after import.

Instructions

Importar Empleados a SIIGO (funcion PUSHEMPL de SIIGO Pyme). Importa a SIIGO el contenido de un archivo .xlsx. El resultado de la importacion queda en la carpeta TEMP de la empresa correspondiente.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoAnio de proceso en SIIGO, 4 digitos. Por defecto el anio configurado para la empresa o el actual.
claveNoClave del usuario, hasta 8 caracteres. Por defecto la configurada. Nunca se devuelve en las respuestas.
normaNoNorma de la que se extrae la informacion: L = local (PUC colombiano), N = NIIF. Por defecto L.
empresaYesEmpresa sobre la que ejecutar. Acepta la ruta completa (Z:\SIIWI01\), solo el numero (01) o un alias configurado. Use siigo_list_companies para ver las disponibles.
usuarioNoUsuario de SIIGO, hasta 8 caracteres. Por defecto el configurado para la empresa.
logErroresNoRuta donde dejar el log de errores de la importacion. Ej: C:\SIIWI01\LOGS\ErrorEmpleados.xlsx. Si se omite, el servidor genera una ruta corta.
instalacionNoCarpeta de la instalacion de SIIGO a usar (por ejemplo C:\Siigo2). Por defecto la asociada a la empresa.
archivoEntradaYesRuta completa del .xlsx con la informacion a importar, maximo 50 caracteres. Ej: C:\SIIWI01\Empleados.xlsx.
Behavior3/5

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

The annotations already indicate destructiveHint=true, and the description adds one behavioral detail: the result is placed in the company's TEMP folder. However, it does not elaborate on side effects, permission requirements, or error handling, providing only minimal additional context beyond the annotations.

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?

The description is two sentences long, front-loads the tool's purpose, and includes the function name and output location without any filler or repetition.

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

Completeness2/5

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

For a destructive import operation with no output schema, the description is sparse. It mentions the TEMP folder destination but fails to explain the process, potential overwriting behavior, error handling, or prerequisites. Given the tool's complexity (8 parameters) and destructive nature, this is not sufficiently complete.

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?

The input schema provides full descriptions for all eight parameters, so the description adds no additional parameter semantics. The mention of .xlsx is redundant with the schema's archivoEntrada description. Baseline of 3 is appropriate given 100% schema coverage.

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 description clearly states the tool imports employee data from an .xlsx file into SIIGO using the PUSHEMPL function. It distinguishes itself from sibling tools (e.g., pushext, pushmov) by explicitly referencing 'Empleados' and the specific function name, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for importing employee data but provides no explicit guidance on when to use this tool over alternatives, nor does it mention any prerequisites or exclusions. It simply states what the tool does without contextualizing its selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/javalenciacai/siigo-pyme-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server