Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Movimiento Contable de Cajero

siigo_getmvt
Read-only

Extract cashier accounting movement data from SIIGO Pyme, generate an .xlsx file, and return parsed preview rows.

Instructions

Extraer Movimiento Contable de Cajero (funcion GETMVT de SIIGO Pyme). Genera un archivo .xlsx y devuelve sus primeras filas ya parseadas.

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.
conDatosNoS = tomar datos de SIIGO, N = generar solo el encabezado (plantilla vacia).
nroFinalNoNumero de comprobante final, 11 digitos. Ej: 99999999999.
fechaFinalYesFecha final dentro del anio de proceso, formato MMDD. Ej: 0530. Tambien acepta 2026-05-30.
nroInicialNoNumero de comprobante inicial, 11 digitos. Ej: 00000000001.
cuentaFinalNoCuentaFinal: cuenta contable final, 10 digitos. Ej: 1110050100.
instalacionNoCarpeta de la instalacion de SIIGO a usar (por ejemplo C:\Siigo2). Por defecto la asociada a la empresa.
fechaInicialYesFecha inicial dentro del anio de proceso, formato MMDD. Ej: 0517. Tambien acepta 2026-05-17.
filasPreviewNoCuantas filas del xlsx generado incluir en la respuesta. Por defecto 50; use 0 para no leer el archivo.
modeloBasicoNoN = exporta toda la informacion solicitada. S = genera el modelo basico.
archivoSalidaNoRuta completa del .xlsx a generar, maximo 50 caracteres. Ej: C:\SIIWI01\MovimientoContableCajero.xlsx. Si se omite, el servidor genera una ruta corta dentro de su carpeta de salida. Si se pasa un nombre sin ruta, SIIGO lo deja en la carpeta Documentos del usuario.
cuentaInicialNoCuentaInicial: cuenta contable inicial, 10 digitos. Ej: 1105050100.
productoFinalNoProducto final, 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 9999999999999.
productoInicialNoProducto inicial, 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 0010001000001.
tipoComprobanteNoTipo de comprobante: * = todos, F = facturas, etc. Un solo caracter.
codigoComprobanteFinalNoCodigo de comprobante final a exportar, 3 digitos. Ej: 002.
codigoComprobanteInicialNoCodigo de comprobante inicial a exportar, 3 digitos. Ej: 001.
Behavior3/5

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

Annotations already provide read-only and non-destructive hints. The description adds the non-obvious behavior that the tool writes a .xlsx file and returns a parsed preview, which is useful. It does not disclose file lifecycle, required credentials, or what happens if the file already exists, but given annotation coverage, this is adequate.

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 description is a single front-loaded sentence with no filler. It communicates the core purpose and output efficiently, though it could perhaps include a pointer to usage guidance without much cost.

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

Completeness3/5

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

For a 21-parameter extraction tool with no output schema, the one-sentence description is thin but the schema is very rich and annotations cover safety. It states the file-generation and preview behavior but omits error handling, prerequisites, and relationship to sibling tools, leaving moderate gaps.

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?

All 21 parameters are described in the schema with 100% coverage, so the description carries no parameter burden. The description adds no parameter-specific semantics beyond the schema, keeping it at the baseline.

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 uses a specific verb 'Extraer' and names the exact SIIGO function (GETMVT) plus the resource 'Movimiento Contable de Cajero'. It also states the output behavior (generates .xlsx and returns parsed rows). However, it does not explicitly differentiate from the similar sibling 'siigo_getmov', so it loses some distinction points.

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

Usage Guidelines2/5

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

No guidance is given on when to choose this tool over siblings like siigo_getmov or siigo_getext. The description simply states what the tool does, leaving the agent to infer usage context from the name and schema.

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