Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Documentos ExtraContables

siigo_getext
Read-only

Extract extra-accounting documents from SIIGO Pyme, generate an .xlsx file, and return the first parsed rows for immediate use.

Instructions

Extraer Documentos ExtraContables (funcion GETEXT 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.
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.
archivoSalidaNoRuta completa del .xlsx a generar, maximo 50 caracteres. Ej: C:\SIIWI01\DocExtraContable.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.
tipoComprobanteNoTipo de comprobante: * = todos, Z = orden de pedido, Y = orden de compra, V = cotizacion.
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 declare readOnlyHint=true and destructiveHint=false. The description adds that it generates an .xlsx file and returns its first rows parsed, which is useful but does not cover details like file persistence, overwrite behavior, or response format.

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 concise, front-loaded sentences. It states the main purpose and key behaviors without any redundant or filler content.

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?

Given the tool's complexity (16 parameters, no output schema), the description is minimal. It provides a high-level summary and mentions parsed rows, but it does not explain required parameters, prerequisites, or typical usage workflows, leaving gaps for a complete mental model.

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 100%, with each of the 16 parameters having detailed descriptions and examples. The tool description adds no parameter-level detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 extracts extra-accounting documents via the GETEXT function of SIIGO Pyme. It uses the specific verb 'Extraer' and resource 'Documentos ExtraContables', distinguishing it from sibling extraction tools like siigo_getmov or siigo_getlis.

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 provided on when to use this tool versus alternatives. The description only states what it does and offers no context about when to select it over other SIIGO extraction tools.

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