Skip to main content
Glama

bcn_comparar_versiones

Read-only

Compare the literal text of a Chilean code or law across two dates to detect legal reforms, gaps, and prior-law effects on pending proceedings.

Instructions

Compara el tenor literal de un código o ley chilena en dos fechas (diff intertemporal BCN) para detectar reformas legales, vacancia legal y ultraactividad procesal.

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": "<norma>",
      "fecha_a": "<fecha_a>"
    },
    "name": "bcn_comparar_versiones"
  }
}

Input Schema

NameRequiredDescriptionDefault
normaYesNombre del código ('trabajo', 'civil', 'cpc') o número de ley ('19.300', '21643')
fecha_aYesFecha histórica inicial en formato YYYY-MM-DD
fecha_bNoSegunda fecha YYYY-MM-DD (si se omite, compara contra la versión vigente actual)
articuloNoNúmero de artículo específico a comparar (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds domain-relevant framing (the output is a diff intended to reveal reforms and vacancy) but says nothing about the shape of that diff, size limits, or how the open-world lookup behaves when a norm or date is not found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and resource, then the analytical payoff. No filler, no repetition of schema details, and nothing an agent must read past to get the core meaning.

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?

For a 4-parameter, fully documented schema with annotations covering safety, the description is nearly sufficient: purpose, domain framing and the comparison semantics are all present. The one gap is that no output schema exists and the description does not indicate what the diff result looks like or how it is structured.

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 each of the four parameters is already documented with format and defaults in the schema. The description only restates the two-date comparison and adds no syntax, naming conventions, or edge-case guidance (e.g. what happens if fecha_b precedes fecha_a) beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Compara el tenor literal de un código o ley chilena en dos fechas', and frames it as an 'diff intertemporal' aimed at detecting reforms, legal vacancy and ultraactivity. That is clearly distinct from a plain historic-fetch tool, but no sibling (e.g. bcn_get_codigo_historico) is named to reinforce the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'para detectar reformas legales, vacancia legal y ultraactividad procesal' implies the analytical use case, so an agent can infer when this tool is appropriate. However, it never states when not to use it or which sibling to pick for a simple version lookup versus an intertemporal comparison.

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