Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Comparar dos artículos de normas distintas

comparar_articulos

Compare article text between two Colombian norms, mark added/removed text, and classify differences (e.g., deadline, sanction). Use con_reforma to compare against the portal's noted reform.

Instructions

Compara el texto de un artículo entre dos normas, 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». 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 (la página consolida; no publica la redacción anterior). Sin modelo semántico.

Input Schema

TableJSON 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.5/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 discloses the classification taxonomy, the Dice bigram similarity threshold (≥0.92), the 'revisar manualmente' fallback for unmatched text, the absence of a semantic model, and a key limitation — that the portal consolidates text and does not publish the prior wording, so the comparison is against the last reform rather than a full history.

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 action and efficient overall, but the single dense paragraph with multiple parenthetical asides is slightly run-on and could be split for easier scanning.

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 exists, and the description compensates by describing the result content (marked diffs, classification, manual-review flag) and the con_reforma caveat. It stops short of specifying the response structure, which leaves a small gap for a tool with no output schema.

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, but the description adds real meaning beyond the schema by clarifying that norma_b/articulo_b are unused under con_reforma=true and what that flag actually triggers (locating the last annotated reform and extracting the modifying article).

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 (compare one article's text across two norms) and further specifies the output behavior: marking additions/deletions, classifying differences, and flagging unmatched cases. This is clearly distinct from sibling tools like buscar_normas or historial_norma, which retrieve rather than diff.

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 explains the two operating modes and when each applies: default two-norm comparison, or con_reforma=true when only one norm is available. It does not name sibling alternatives or state when NOT to use this tool, so it falls short of a full 5.

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