Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Saldos Cuentas por Cobrar o Cuentas por Pagar

siigo_getsal
Read-only

Extract accounts receivable or payable balances from SIIGO Pyme into an Excel file, with parsed preview rows returned.

Instructions

Extraer Saldos Cuentas por Cobrar o Cuentas por Pagar (funcion GETSAL 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).
fechaCorteNoFecha de corte dentro del anio de proceso, formato MMDD. Ej: 0530.
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.
filasPreviewNoCuantas filas del xlsx generado incluir en la respuesta. Por defecto 50; use 0 para no leer el archivo.
saldoCuentasNo* = todos, C = cuentas por cobrar, P = cuentas por pagar.
terceroFinalNoTercero (NIT) final, hasta 13 digitos. Ej: 9999999999999.
archivoSalidaNoRuta completa del .xlsx a generar, maximo 50 caracteres. Ej: C:\SIIWI01\SaldosCartera.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.
aCorteAnteriorNoS = genera saldos a corte anterior, N = no los genera.
terceroInicialNoTercero (NIT) inicial, hasta 13 digitos. Ej: 1.
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool creates an .xlsx file and returns it already parsed, which is critical behavioral information. It does not mention configurable preview row counts or file path behaviors, but these are documented in the schema.

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: the first states the exact purpose, the second summarizes the output behavior. No fluff or redundancy.

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 16 parameters and no output schema, the description gives a high-level overview but leaves the structure of the parsed rows unspecified. It adequately complements the schema but is not fully complete for an agent needing to infer return shape without additional cues.

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 already describes all 16 parameters with 100% coverage, including defaults and examples. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 specific function: extracting AR/AP balances via the SIIGO GETSAL function, and explicitly mentions it generates an .xlsx file and returns the first parsed rows. This distinguishes it from sibling tools like siigo_getmov or siigo_read_xlsx.

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 provides clear context for when to use the tool: whenever AR/AP balances need to be extracted. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough that an agent can decide without confusion.

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