Skip to main content
Glama
javalenciacai

siigo-pyme-mcp

Extraer Maestro de Seriales

siigo_getsrl
Read-only

Export SIIGO Pyme serial master data to an Excel file and get parsed preview rows, enabling direct access to serial records.

Instructions

Extraer Maestro de Seriales (funcion GETSRL 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.
estadoNoD = disponible, N = no disponible, T = todos.
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.
serialFinalNoSerial final, hasta 25 caracteres. Ej: zzzzzzzzzzzzzzzzzzzzzzzzz.
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\MaestroSeriales.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, 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 9999999999999.
serialInicialNoSerial inicial, hasta 25 caracteres. Ej: * (todos).
productoInicialNoProducto inicial, 13 digitos (linea 3 + grupo 4 + producto 6). Ej: 0010001000001.
Behavior1/5

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

The description states 'Genera un archivo .xlsx' (generates an .xlsx file), which implies a file-system side effect and contradicts the annotation readOnlyHint=true. This is an explicit contradiction between the description and the annotations.

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 concise (two sentences) and front-loaded with the primary purpose. It includes the underlying SIIGO function name and the core action, with no redundant or misleading 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 14 parameters and no output schema, the description conveys the essential workflow (extracción, generación de xlsx, parsing de filas) but lacks high-level context about the meaning of the result, prerequisites, or how the parameters interact. The schema covers individual parameters, so the description is minimally adequate.

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 provides 100% descriptor coverage for all 14 parameters, with detailed explanations and examples. The tool description adds no additional parameter context, so the baseline score 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 explicitly names the tool's purpose with a specific verb and resource: 'Extraer Maestro de Seriales (funcion GETSRL de SIIGO Pyme).' It further clarifies the output behavior (generates an .xlsx and returns parsed rows), which disambiguates it from other sibling tools.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The only reference to another tool ('siigo_list_companies') appears in the input schema, not in the main description.

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