Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Productos de Inventarios

siigo_getinv
Read-only

Extracts product inventories from SIIGO Pyme, generates an Excel (.xlsx) file, and returns the first rows parsed for immediate use.

Instructions

Extraer Productos de Inventarios (funcion GETINV 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).
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.
archivoSalidaNoRuta completa del .xlsx a generar, maximo 50 caracteres. Ej: C:\SIIWI01\Productos.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.
productoFinalNoProducto final, hasta 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 9999999999999.
productoInicialNoProducto inicial, hasta 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 0010001000001.
Behavior4/5

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

The description adds behavioral context beyond annotations: it generates an .xlsx file and returns parsed preview rows. This is useful, though it does not detail return structure or file side effects. However, annotations already declare read-only and non-destructive behavior, so the added value is appropriate.

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 sentences, front-loaded with the core purpose and output behavior, with no redundant information. Every word 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?

The description explains the tool's output (xlsx generation and parsed preview) and leverages the detailed schema for parameters. It lacks an explicit return structure, but given the annotations and schema richness, it is mostly adequate for an agent to understand the tool's function.

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 has full parameter descriptions, covering all 11 properties with details like defaults and examples. The tool description itself adds no extra parameter semantics beyond what the schema provides, so the baseline score 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 tool extracts inventory products via the GETINV function, generates an .xlsx file, and returns parsed preview rows. This specific verb+resource combination distinguishes it from sibling tools like siigo_getmov or siigo_pushinv.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives or mention exclusions. The use case is implied by the title and description, but there is no direct guidance on prerequisites or alternative tools. The only hint is in the 'empresa' parameter description referring to siigo_list_companies.

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