Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Informes

siigo_getinf
Read-only

Generates SIIGO Pyme trial balance reports as Excel files and returns the first parsed rows, enabling quick financial analysis.

Instructions

Extraer Informes (funcion GETINF de SIIGO Pyme). Genera un archivo .xlsx y devuelve sus primeras filas ya parseadas. El manual reusa NitInicial/NitFinal para el rango de cuentas cuando tipoInforme es BCC. El ejemplo del manual para BCC escribe B en lugar de BCC; es una errata del manual.

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.
mesFinalNoMes final, 2 digitos. Ej: 12.
nitFinalNoCon tipoInforme B es el tercero final (hasta 13 digitos). Con BCC es la cuenta final (hasta 10 digitos).
mesInicialNoMes inicial, 2 digitos. Ej: 03.
nitInicialNoCon tipoInforme B es el tercero inicial (hasta 13 digitos). Con BCC es la cuenta inicial (hasta 10 digitos).
instalacionNoCarpeta de la instalacion de SIIGO a usar (por ejemplo C:\Siigo2). Por defecto la asociada a la empresa.
tipoInformeYesB = balance de comprobacion por tercero, BCC = balance de comprobacion por cuenta.
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\BALANCEPORTERCEROS.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.
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 and returns parsed rows, plus a manual errata warning. It doesn't disclose permissions, rate limits, or output structure, but the annotations cover the safety profile.

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 four concise sentences, front-loaded with the primary purpose, and contains no filler. Every sentence provides value, from the core behavior to the manual errata warning.

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?

With 13 parameters and no output schema, the description explains the high-level behavior but doesn't detail the structure of the returned rows or the generated file's handling. The schema covers many details, but more context on the output format would improve 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 100%, so baseline is 3. The description's note about NitInicial/NitFinal being reused for BCC and the manual errata is a minor clarification, largely redundant with the schema parameter descriptions.

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 clearly states it extracts reports via SIIGO's GETINF function and generates an .xlsx file with parsed first rows. It distinguishes itself from sibling get* tools by focusing on report generation, but doesn't explicitly name the report types B/BCC in the description.

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?

There is no guidance on when to use this tool versus alternative siigo_get* tools, nor typical use cases. The only caveat about the manual's parameter reuse for BCC relates to parameter handling, not tool 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