Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Maximos y Minimos por Bodegas

siigo_getbodm
Read-only

Retrieve maximum and minimum stock levels by warehouse from SIIGO Pyme and export to Excel. Generates an .xlsx file with preview rows for analysis.

Instructions

Extraer Maximos y Minimos por Bodegas (funcion GETBODM 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).
bodegaFinalNoBodega final, 4 digitos. Ej: 9999.
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\maximos_y_minimos_por_bodega.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.
bodegaInicialNoBodega inicial, 4 digitos. Ej: 0001.
productoFinalNoProducto final, 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 9999999999999.
productoInicialNoProducto inicial, 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?

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds useful context by disclosing that the tool generates an .xlsx file and returns its first parsed rows. This goes beyond the annotations and helps the agent understand the side effect of file creation and the preview behavior.

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 extremely concise: two sentences that pack the function name, purpose, and output behavior. No filler or redundant wording; every clause 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?

For a tool with 13 parameters and no output schema, the description gives a clear outcome (generates xlsx, returns parsed first rows) and the schema covers all parameters. It could have explained more about the exact structure of the returned rows, but given the strong schema, it is sufficiently complete.

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 coverage is 100%, so all 13 parameters have detailed descriptions in the input schema. The description adds no additional parameter-level semantics. Baseline of 3 is appropriate since the schema carries the full informational burden.

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 verb ('Extraer') and resource ('Maximos y Minimos por Bodegas'), and further specifies it calls the SIIGO Pyme GETBODM function. It distinguishes itself from sibling tools by naming the exact function and output (an .xlsx file with parsed first rows).

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 explicit guidance is provided about when to use this tool versus alternatives like siigo_getbod or siigo_getbop. The description only states what it does, leaving the agent to infer usage from the title. There is no mention of alternatives or exclusions.

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