Skip to main content
Glama
Normativa Colombia MCP

Normativa Colombia MCP

Comparar dos artículos de normas distintas

comparar_articulos
Read-onlyIdempotent

Compare a Colombian legal article across two norms to mark added and removed text, classify each difference, and flag items needing manual review; optionally compare it against its latest reform.

Instructions

Compara el texto de un artículo entre dos normas y marca lo añadido y lo eliminado. Clasifica cada diferencia por patrones de texto (plazo, sanción, excepción, sujeto obligado, prohibición u obligación) y detecta cambios editoriales por similitud léxica (Dice bigramas, ≥0,92); lo que no encaja se marca «revisar manualmente». Sin modelo semántico. Con con_reforma=true no hace falta la segunda norma: busca la última reforma que el portal anota al artículo, extrae el artículo de la norma modificadora y lo contrasta con el texto vigente, porque la página consolida y no publica la redacción anterior. Para ver todas las reformas de la norma usa historial_norma; para reunir evidencia de un conflicto entre dos normas enteras, analizar_conflicto.

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": {
      "norma_a": "<norma_a>",
      "articulo_a": "<articulo_a>"
    },
    "name": "comparar_articulos"
  }
}

Input Schema

NameRequiredDescriptionDefault
norma_aYesCita de la norma base, ej. "Ley 909 de 2004"
norma_bNoCita de la segunda norma, ej. "Decreto 1083 de 2015"; no se usa con con_reforma=true
articulo_aYesNúmero del artículo de la norma base, ej. "31"
articulo_bNoNúmero de artículo de la segunda norma; no se usa con con_reforma=true
con_reformaNotrue: compara el artículo contra la última reforma que el portal le anota (no pidas norma_b)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.15.1
    • changedInput schema / properties / articulo_a / description
      Previous value: -"Número de artículo de la primera norma, ej. \"12\""New value: +"Número del artículo de la norma base, ej. \"31\""
    • changedInput schema / properties / articulo_b / description
      Previous value: -"Número de artículo de la segunda norma, ej. \"12\""New value: +"Número de artículo de la segunda norma; no se usa con con_reforma=true"
    • addedInput schema / properties / con_reforma
      Added value: +{
      +  "default": false,
      +  "description": "true: compara el artículo contra la última reforma que el portal le anota (no pidas norma_b)",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / norma_a / description
      Previous value: -"Cita de la primera norma, ej. \"Ley 909 de 2004\""New value: +"Cita de la norma base, ej. \"Ley 909 de 2004\""
    • changedInput schema / properties / norma_b / description
      Previous value: -"Cita de la segunda norma, ej. \"Decreto 1083 de 2015\""New value: +"Cita de la segunda norma, ej. \"Decreto 1083 de 2015\"; no se usa con con_reforma=true"
    • changedInput schema / required
      Previous value: -[
      -  "norma_a",
      -  "articulo_a",
      -  "norma_b",
      -  "articulo_b"
      -]New value: +[
      +  "norma_a",
      +  "articulo_a"
      +]
  2. Addedv1.10.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent operation, but the description adds substantial behavior beyond them: the classification method (text patterns for plazo/sanción/excepción/etc.), the Dice-bigram threshold of ≥0.92, the 'revisar manualmente' fallback, the absence of a semantic model, and the non-obvious portal behavior behind con_reforma. This is exactly the kind of context annotations cannot carry.

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 comparison action, then the method, then the con_reforma caveat, then sibling routing; every sentence carries information. It is dense and slightly run-on, but no sentence is filler given the tool's complexity.

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 comparison tool with no output schema and full schema description coverage, the description supplies the missing return semantics (added/removed marking, difference categories, manual-review bucket) and both operating modes. Nothing essential for correct invocation is absent.

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 the baseline is 3. The description goes beyond it by clarifying the interaction semantics of con_reforma — that norma_b (and articulo_b) need not be supplied, and why the tool can infer the counterpart article from the portal's annotated reform. That adds real meaning over the schema's per-field text.

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 specific verbs and resource: comparing article text between two norms, marking additions/deletions, classifying differences by patterns, and detecting editorial changes by lexical similarity. It explicitly names what it is not for ('Sin modelo semántico') and names siblings (historial_norma, analizar_conflicto), so an agent can distinguish it 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 explicit conditional usage: use con_reforma=true when you don't have the second norm, and explains why (the portal consolidates and doesn't publish prior wording). It then routes to alternatives with conditions: historial_norma for all reforms of a norm, analizar_conflicto for whole-norm conflicts. When-to-use and when-to-use-something-else are both covered.

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