Skip to main content
Glama

cemis-directorio

by io.github.francofuji

Impacto de una reforma

impacto_de_reforma
Read-onlyIdempotent

Herramienta principal: dado el número o título (exacto o aproximado) de una transformación/reforma de 2026, devuelve su impacto sobre el directorio CEMIS.

El criterio de impacto varía según la naturaleza de la reforma (ver
ambito_transformaciones.py, curado a mano transformación por transformación):
- Reformas cuyo alcance real es un TIPO de empresa (estatal/no estatal/
  inversión extranjera/cooperativa) matchean por tipo, no por sector, y el
  resultado lo indica con "criterio_de_impacto": "tipo_de_empresa".
- Reformas TRANSVERSALES (fiscales/cambiarias/laborales de alcance nacional,
  o que explícitamente aplican a "todos los actores económicos") devuelven
  "alcance": "transversal" con la metadata de la reforma, sin enumerar las
  252 empresas del directorio (no aporta valor).
- Reformas que NO APLICAN a un actor económico del directorio (reforma de
  aparato de gobierno, política social para personas, deuda soberana) lo
  dicen explícitamente en vez de devolver un array vacío sin explicación.
- El resto matchea por SECTOR de industria vía EMPRESA_SECTOR_KEYWORDS
  (mismo criterio que cemis.io, con el fix de normalización de acentos
  de 2026-08-23 — antes "turis" no matcheaba "turística").

En todos los casos incluye oportunidades_directas (vínculo curado
transformacion_num) y el estado de implementación regulatoria si está
disponible (ver monitor de reformas de cemis.io).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transformacionYes

TDQS

A4.4/5.0
Behavior5/5

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

The description goes far beyond the readOnly/idempotent annotations: it details type-of-company versus sector matching, the 'alcance': 'transversal' behavior, explicit non-application messages instead of empty arrays, accent normalization behavior, and the inclusion of oportunidades_directas and regulatory implementation state. No contradiction with 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the bulleted structure makes a complex set of behaviors scannable. Some internal code references and the dated normalization footnote add length, but they carry meaningful behavioral detail rather than filler.

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?

Given the absence of an output schema, the description explains response variants, the no-empty-array guarantee, and the included fields reasonably well. It does not spell out the exact response envelope or the not-found case, but for a one-parameter tool it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides a bare 'transformacion' string with no description. The tool description compensates fully by explaining that it accepts the exact or approximate number/title of a 2026 reform and even illustrates fuzzy matching with the 'turis'/'turística' normalization fix.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a clear action ('devuelve su impacto sobre el directorio CEMIS') and a specific input ('número o título ... de una transformación/reforma de 2026'). It clearly differs from siblings like buscar_empresas, but it never names or directly contrasts them.

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: this is the main tool for reform-impact queries and explains how impact criteria vary by reform type. It does not explicitly list exclusions or alternative sibling tools, but the intended usage is unambiguous.

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

All cemis-directorio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct query path: general company search, full company profile, opportunity-to-company lookup, sector-to-opportunity lookup, reform impact, and list helpers. Even the related entity lookups are clearly separated by input and output.

Naming Consistency3/5

Names are readable and consistently lowercase with underscores, but they mix verb-first conventions (buscar_empresas, listar_sectores) with noun-first descriptive names (ficha_empresa, impacto_de_reforma, empresas_por_oportunidad). The pattern is understandable but not uniform.

Tool Count5/5

Seven tools is well within the ideal range and each tool covers a necessary query path for the CEMIS directory domain. There is no obvious bloat or thinness in the tool surface.

Completeness4/5

The core workflows are well covered: company search, company detail, sector/province enumeration, sector-opportunity relationships, opportunity-company relationships, and reform impact. Minor gaps exist, such as no direct way to list all reforms or all opportunities, but these can be worked around through the existing sector and reform lookup tools.

Resources