Skip to main content
Glama
edpauce

ISO Agents

by edpauce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

4.1 · Matriz de cuestiones internas y externas

contexto_cuestiones_4_1

Generates or updates the Annex SL clause 4.1 context matrix for internal and external issues, adapting to your sector and Peru's legal framework.

Instructions

Genera la Matriz de Contexto (cuestiones internas y externas) del requisito 4.1 del Anexo SL (ISO 9001/14001/45001), aterrizada al sector y al marco legal peruano. Admite documento del cliente (documentoCliente/documentoClientePath), modo generar|actualizar y formato casa|cliente.

Input Schema

NameRequiredDescriptionDefault
modoNogenerar = crear de cero con la metodología casa (default). actualizar = partir del documento del cliente, conservar lo correcto y actualizarlo/reforzarlo a la versión vigente de la norma. 'actualizar' requiere un documento.
nombreYesRazón social o nombre de la empresa.
normasNoNormas ISO objetivo del sistema de gestión. Por defecto ISO 9001. Usa 37001 para sistemas de gestión antisoborno (SGAS).
sectorYesSector / rubro económico (ej. 'Distribución de energía eléctrica').
tamanoNoTamaño o nº de trabajadores (texto libre, admite rangos: '51-200').
formatoNocasa = plantilla estándar de la casa (default). cliente = replicar la estructura, columnas, escala y metodología del documento del cliente. 'cliente' requiere un documento.
materialNoMaterial fuente OPCIONAL: texto extraído de documentos reales del cliente (políticas, actas, informes) para fundamentar la generación (grounding).
procesosNoProcesos principales de la organización.
ubicacionNoPaís / región de operación. Por defecto se asume Perú (marco legal peruano).
salidaPathNoCarpeta o ruta de archivo .docx donde escribir la salida. Por defecto: carpeta 'salidas/' del proyecto.
exportarDocxNoSi es true, además del Markdown genera un archivo Word (.docx) con formato casa (tablas y colores) y devuelve su ruta para abrirlo en Word.
plantillaPathNoRuta a una PLANTILLA .docx del cliente con marcadores docxtemplater ({campo}, {#bucle}…{/bucle}). Si se da, rellena esa plantilla conservando su formato visual EXACTO (colores, bordes, logo) y devuelve la ruta del .docx generado.
documentoClienteNoTexto del documento VIGENTE del cliente (matriz previa, política, acta, FODA anterior). Base para grounding, actualización o para replicar su formato.
productosServiciosNoProductos y servicios principales de la organización.
documentoClientePathNoRuta local a un documento del cliente (.docx/.txt/.md) que el servidor leerá y usará como base. Alternativa a documentoCliente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that output is tailored to sector and Peruvian legal framework and that client documents and modes are supported, but it does not explain file-writing side effects, overwrite behavior, permissions, or error conditions for a generation tool with 15 parameters.

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?

Two sentences, front-loaded with the core purpose and followed by key accepted inputs and modes. There is no filler, and the structure makes the main action immediately clear.

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?

The schema is rich and fully described, which covers parameter semantics. However, for a complex generation tool with no output schema and no annotations, the description does not mention expected output format, file side effects, or important operational constraints beyond the brief mention of client documents and modes.

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 the schema already documents all parameters thoroughly. The description mentions documentoCliente/documentoClientePath, modo generar|actualizar and formato casa|cliente, but this largely repeats what the schema provides rather than adding new semantic detail.

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?

States a specific verb and resource: genera la Matriz de Contexto (cuestiones internas y externas) for requirement 4.1 of Anexo SL. The resource is clearly differentiated from sibling tools such as FODA, PESTEL, partes interesadas, alcance and mapa de procesos.

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 implies usage by tying the tool to requirement 4.1 and mentioning generar|actualizar and casa|cliente modes. However, it does not explicitly state when to use this tool versus the sibling contexto_foda_4_1, contexto_pestel_4_1 or other contexto tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools