Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar normativa de un regulador sectorial

buscar_normativa_sectorial

Search administrative acts from Colombian sector regulators and ministries. Ideal for resolutions, circulars, and agreements not cataloged in the central norm database.

Instructions

Actos administrativos —resoluciones, circulares, acuerdos— de los reguladores y ministerios sectoriales que el Gestor Normativo NO cataloga; elige cuál en entidad. CUÁNDO NO USARLA: para leyes y decretos nacionales de cualquier sector usa resolver_cita o buscar_por_tema, que dan texto completo y vigencia; el Decreto Único Reglamentario de cada sector (1071, 1072, 1074, 1076, 1079…) ya está en el Gestor. Casi todas entregan PDF sin texto extraíble, y la mayoría no publica estado de vigencia; donde aparece (ANM, Supersociedades) es la fila del propio portal, no una verificación: para el estado real de una ley o un decreto, resolver_cita. LOS FILTROS NO SE COMPORTAN IGUAL EN TODAS: el Invima exige texto o año; la Superfinanciera y la Supertransporte se quedan en el año en curso si no indicas otro; la ANM no aplica el año a las circulares. Cada respuesta dice qué hizo, pero no lo adivines: indica el año si lo esperabas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoAño de cuatro dígitos
textoNoFiltra por número, año o epígrafe
limiteNo
paginaNo
entidadYesRegulador a consultar. Usa describir_fuentes para ver qué sector cubre cada uno.
categoriaNoTipo de acto o categoría (cada fuente declara cuáles soporta; solo Unidad de Víctimas lo filtra hoy)
solo_entidadNoSolo INVIMA/Supersalud: excluye la compilación sectorial del normograma (leyes, decretos y sentencias) y deja solo los actos que la entidad expide (Resolución, Circular…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / properties / solo_entidad / description
      Previous value: -"Solo INVIMA/Supersalud: limita a los actos de los tipos que la propia entidad expide (Resolución, Circular...), excluyendo la compilación sectorial del normograma (leyes, decretos del Ministerio, sentencias)."New value: +"Solo INVIMA/Supersalud: excluye la compilación sectorial del normograma (leyes, decretos y sentencias) y deja solo los actos que la entidad expide (Resolución, Circular…)."
  2. Changed1 schema field changedv1.13.0
    • addedInput schema / properties / solo_entidad
      Added value: +{
+  "description": "Solo INVIMA/Supersalud: limita a los actos de los tipos que la propia entidad expide (Resolución, Circular...), excluyendo la compilación sectorial del normograma (leyes, decretos del Ministerio, sentencias).",
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv1.11.2
    • addedInput schema / properties / categoria
      Added value: +{
+  "description": "Tipo de acto o categoría (cada fuente declara cuáles soporta; solo Unidad de Víctimas lo filtra hoy)",
+  "type": "string"
+}
    • changedInput schema / properties / entidad / enum
      Previous value: -[
-  "minagricultura",
-  "ica",
-  "anm",
-  "supersociedades",
-  "sic",
-  "invima",
-  "superfinanciera",
-  "mintrabajo",
-  "supertransporte",
-  "parques"
-]New value: +[
+  "minagricultura",
+  "ica",
+  "anm",
+  "ant",
+  "supersociedades",
+  "sic",
+  "invima",
+  "superfinanciera",
+  "supersalud",
+  "mintrabajo",
+  "supertransporte",
+  "unidadvictimas",
+  "parques"
+]
  4. Addedv1.9.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it warns that most results are non-extractable PDFs, that validity status is unreliable and only a portal row where present, and that filter behavior differs per source. These are exactly the operational caveats an agent needs and cannot obtain from the schema.

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?

Front-loaded with purpose and a capitalized 'CUÁNDO NO USARLA' block, followed by caveats; every sentence carries usable information. It is dense and long, but no sentence is filler, so it stays within appropriate bounds for a multi-source tool.

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 7-parameter, multi-source tool with no output schema, the description covers the main retrieval and validity pitfalls. It omits operational details like auth needs or pagination behavior beyond limite/pagina, but the described response behavior ('Cada respuesta dice qué hizo') fills the most important gap.

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

Parameters4/5

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

Schema coverage is 71% and the description adds real meaning: it instructs choosing the regulator via `entidad` and details per-source filter behavior (Invima requires texto or año, Superfinanciera/Supertransporte default to the current year, ANM ignores año for circulares). This directly enriches `anio`/`texto`/`entidad` beyond the schema, though it stops short of covering every parameter.

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 (buscar) and resource (actos administrativos de reguladores sectoriales que el Gestor NO cataloga), and immediately distinguishes it from siblings resolver_cita and buscar_por_tema. An agent can tell exactly which corpus this tool covers versus the national law/decreto corpus.

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

Usage Guidelines5/5

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

Contains an explicit 'CUÁNDO NO USARLA' section naming the alternatives (resolver_cita, buscar_por_tema) and the condition that routes to them, plus notes that the Decreto Único Reglamentario is already in the Gestor. When-not and alternatives are both specified.

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