Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Importar Terceros a SIIGO

siigo_pushter
Destructive

Import third-party records from an .xlsx file into SIIGO Pyme using the PUSHTER function. Results are saved in the company's TEMP folder.

Instructions

Importar Terceros a SIIGO (funcion PUSHTER 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\ErrorTer.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\Terceros.xlsx.
Behavior3/5

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

Annotations already signal destructive and non-read-only behavior. The description adds the useful detail that the result is placed in the TEMP folder, but it does not disclose potential overwrites, error handling, or idempotency, which would add extra 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 three concise sentences that front-load the purpose and include the key output location detail without redundancy. Every sentence earns its place.

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?

Given the rich schema, destructive annotation, and straightforward import operation, the description covers the essential purpose and output location. It omits potential error behavior or prerequisites like credential setup, but these are reasonably inferable from the schema and sibling tools, so the overall definition is adequately 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 schema has 100% description coverage across all 8 parameters, so the description does not need to elaborate on parameter meanings. The description contributes no additional parameter-level meaning beyond what the schema already provides, matching the baseline for high 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 title 'Importar Terceros a SIIGO' and description explicitly state the verb (import) and resource (terceros/third parties) via an .xlsx file. It also names the underlying SIIGO function PUSHTER, distinguishing it from sibling push tools.

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 description clearly indicates the use case: importing third-party data from an .xlsx file into SIIGO, with results saved to the TEMP folder. It does not explicitly mention alternatives or exclusions, but the context is unambiguous given the tool name and sibling set.

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