Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Historial de reformas de una norma

historial_norma

Trace the reform history of a Colombian norm: see which rules modified, added, repealed, or replaced it, which article each change affected, and the citable note, grouped by year.

Instructions

Devuelve la cadena de reformas que el Gestor anota sobre una norma: qué norma la modificó, adicionó, derogó, sustituyó... y qué artículo afectó cada cambio, con la nota literal citable. Las ordena por el año de la norma que introduce cada cambio (las notas sin año van al final, sin ordenar) y señala la última reforma ANOTADA, que no es necesariamente la que rige: el portal no siempre anota todas las reformas. La vigencia se consulta con resolver_cita. Con formato="json" devuelve {fecha_consulta, alcance, titulo, url, total, cambios, ultima_reforma, avisos}, solo el objeto.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
citaYesCita de la norma, ej. "Ley 100 de 1993"
desdeNoCuántos cambios saltarse antes de empezar (los demás no caben en la respuesta)
limiteNoCuántos cambios mostrar (hasta 100)
formatoNoSalida: "markdown" (texto legible, por defecto) o "json" (solo el objeto de datos, sin cabecera ni pie)markdown
articuloNoFiltra a las notas de reforma de ese artículo de la norma (ej. "6"); sin él se devuelven todas

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.15.1
    • changedInput schema / properties / articulo / description
      Previous value: -"Filtra a los cambios que afectaron ese artículo (ej. \"6\"); sin él se devuelven todos"New value: +"Filtra a las notas de reforma de ese artículo de la norma (ej. \"6\"); sin él se devuelven todas"
    • addedInput schema / properties / formato
      Added value: +{
+  "default": "markdown",
+  "description": "Salida: \"markdown\" (texto legible, por defecto) o \"json\" (solo el objeto de datos, sin cabecera ni pie)",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "type": "string"
+}
  2. Addedv1.13.0

TDQS

A4.1/5.0
Behavior4/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 discloses ordering behavior (by year, undated notes last and unordered), the crucial caveat that the last ANNOTATED reform is not necessarily the one in force, and that the portal may not annotate all reforms. It omits any auth/rate-limit or failure-mode context, but for a read operation this is rich disclosure.

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 the core purpose, then layered with ordering rules, the caveat, and the alternative. Dense but every sentence carries functional information; only the JSON field enumeration is slightly verbose.

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?

No output schema, but the description compensates by describing the JSON object structure and the ordering/warning semantics. Combined with 100% parameter coverage, an agent has nearly everything needed to invoke and interpret the result.

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 cita, desde, limite, formato and articulo, making 3 the baseline. The description adds the JSON return shape for formato="json", but adds no extra syntax or semantics for the other parameters.

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: returns the chain of reforms the Gestor annotates on a norm, with per-article detail and literal citable notes. It is clearly distinguishable from siblings, notably resolver_cita, which it names for the vigencia query.

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?

Explicitly routes the vigencia use case to resolver_cita and frames this tool as the reform-history source, which is strong context. It does not spell out a full when-not-to-use boundary, so it falls just short of the top score.

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