Skip to main content
Glama
Normativa Colombia MCP

Normativa Colombia MCP

Historial de reformas de una norma

historial_norma
Read-onlyIdempotent

Retrieve the amendment chain of a Colombian norm: which rules modified, added, repealed or substituted it, the article affected, and the literal citable note for each change.

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. articulo filtra primero; desde y limite recortan después esa lista ya ordenada, y la última reforma se calcula sobre todo lo filtrado, no sobre el tramo mostrado. Para la vigencia usa resolver_cita; para los cambios de varias normas a partir de un año, cambios_desde; para comparar el texto antes y después, comparar_articulos. Con formato="json" el objeto trae titulo, url, total, cambios, ultima_reforma y avisos.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cita": "<cita>"
    },
    "name": "historial_norma"
  }
}

Input 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.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly/idempotent/non-destructive), but the description adds the traits that actually matter here: ordering by introducing-norm year, undated notes placed last and unordered, the caveat that the ANNOTATED last reform may not be the one in force because the portal doesn't annotate everything, and how articulo/desde/limite interact with the ordering. This is genuine behavioral disclosure beyond structured data.

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?

One dense paragraph, but front-loaded with purpose, then behavior, then sibling routing, then output shape. Nearly every clause earns its place; it is information-heavy rather than padded, though the density borders on hard to scan.

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?

With no output schema, the description compensates by naming the JSON fields (titulo, url, total, cambios, ultima_reforma, avisos), and it covers pagination semantics, ordering guarantees, the annotation-completeness caveat, and alternatives. An agent has everything needed to call and interpret it.

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 100%, so each parameter is already documented (baseline 3). The description goes further by defining the operation order — articulo filters first, desde/limite trim the already-ordered list afterwards, and ultima_reforma is computed over the full filtered set rather than the shown slice — which the schema does not express.

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+resource ("Devuelve la cadena de reformas... sobre una norma") and enumerates what the chain contains (modificó, adicionó, derogó, sustituyó, artículo afectado, nota literal citable). It is unmistakably distinct from siblings like buscar_normas or consultar_vigencia.

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?

Explicitly routes to three alternatives with their selecting conditions: resolver_cita for vigencia, cambios_desde for multi-norm changes from a year, comparar_articulos for before/after text comparison. Nothing is left to inference.

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