Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar en varias fuentes a la vez

buscar_unificado

Search Gestor Normativo, Corte Constitucional, SUIN-Juriscol, and DIAN in parallel for open queries, aggregating results with source and link.

Instructions

Busca en paralelo en Gestor Normativo, Corte Constitucional, SUIN-Juriscol y DIAN, y agrega los resultados con su fuente y su enlace (con perfil "salud" añade INVIMA y Supersalud; con "mineria", la ANM). Úsala cuando la consulta es abierta o por materia y no hay herramienta obvia; para una cita exacta sigue siendo mejor resolver_cita y para un tribunal concreto, su buscador propio. Cada resultado declara su fuente; la vigencia de SUIN se rotula SEGÚN EL BUSCADOR y no es la ficha oficial. Cuando la fuente sirve su texto, cada resultado trae "Para leer", la llamada lista a obtener_documento. Con formato="json" devuelve un objeto con fecha_consulta, alcance, texto, resultados (cada uno con su "Para leer" cuando existe), sin_resultados, fallidas y avisos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textoYesTérminos a buscar, ej. "teletrabajo"
limiteNoCuántos resultados por fuente (máximo 30)
perfilNoPerfil sectorial: prioriza la fuente que mejor responde a ese sector (tributario → DIAN; salud → INVIMA y Supersalud; mineria → ANM)
formatoNoSalida: "markdown" (texto legible, por defecto) o "json" (un objeto con fecha_consulta, alcance, texto, resultados, sin_resultados, fallidas y avisos, sin cabecera ni pie)markdown
fuentesNoFuentes a consultar; sin él se usan todas menos DIAN (que va con perfil=tributario)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.1
    • addedInput schema / properties / formato
      Added value: +{
+  "default": "markdown",
+  "description": "Salida: \"markdown\" (texto legible, por defecto) o \"json\" (un objeto con fecha_consulta, alcance, texto, resultados, sin_resultados, fallidas y avisos, sin cabecera ni pie)",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.13.0
    • changedInput schema / properties / fuentes / items / enum
      Previous value: -[
-  "gestor",
-  "corte",
-  "suin",
-  "dian"
-]New value: +[
+  "gestor",
+  "corte",
+  "suin",
+  "dian",
+  "invima",
+  "supersalud",
+  "anm"
+]
    • changedInput schema / properties / perfil / description
      Previous value: -"Perfil sectorial: prioriza la fuente que mejor responde a ese sector (tributario → DIAN)"New value: +"Perfil sectorial: prioriza la fuente que mejor responde a ese sector (tributario → DIAN; salud → INVIMA y Supersalud; mineria → ANM)"
    • changedInput schema / properties / perfil / enum
      Previous value: -[
-  "laboral",
-  "tributario",
-  "ambiental",
-  "contratacion",
-  "energia"
-]New value: +[
+  "laboral",
+  "tributario",
+  "ambiental",
+  "contratacion",
+  "energia",
+  "salud",
+  "mineria"
+]
  3. Addedv1.11.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries real weight: it discloses parallel execution, per-source attribution ('cada resultado declara su fuente'), the important caveat that SUIN vigencia is labeled 'SEGÚN EL BUSCADOR' and is not the official ficha, the profile-dependent source expansion, and the 'Para leer' handoff to obtener_documento. It does not address rate limits or explicitly state read-only nature, but for a search tool the behavioral picture is strong.

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?

Purpose and the source list are front-loaded, followed by routing guidance and output behavior. It is a dense single paragraph, but every clause (profiles, vigencia caveat, json shape) earns its place with little padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter tool with no output schema and no annotations, the description compensates well: it explains the json return object fields (fecha_consulta, alcance, texto, resultados, sin_resultados, fallidas, avisos) and the markdown-vs-json difference, so an agent knows what to expect from either format.

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 baseline is 3, and most param detail in the description (perfil union of sectors, fuentes default excluding DIAN, formato json field list) is duplicated from the schema field descriptions. The description adds only marginal meaning beyond what the schema already documents.

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 (busca) and resource (múltiples fuentes jurídicas nombradas: Gestor Normativo, Corte Constitucional, SUIN-Juriscol, DIAN), and explicitly distinguishes itself from siblings by naming resolver_cita for exact citations and 'su buscador propio' for a specific tribunal. An agent can pick this apart from the individual source tools without opening any schema.

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?

Gives an explicit when-to-use ('cuando la consulta es abierta o por materia y no hay herramienta obvia') plus when-not/alternatives ('para una cita exacta sigue siendo mejor resolver_cita', 'para un tribunal concreto, su buscador propio'). Routing is unambiguous for the sibling list provided.

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