Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar jurisprudencia del Consejo de Estado

buscar_jurisprudencia_consejo_estado

Search Colombia's Council of State rulings on administrative law, contracts, elections, and direct reparations; each result includes the legal issue, answer, and SAMAI link.

Instructions

Providencias tituladas del Consejo de Estado, el supremo de lo contencioso administrativo (nulidad y restablecimiento, contratación estatal, nulidad electoral, reparación directa, conceptos de la Sala de Consulta): tribunal DISTINTO de la Corte Constitucional y de la Suprema. Cada resultado trae el problema jurídico y su respuesta, más el enlace a la ficha en SAMAI. CÓMO BUSCA: con exacto=true (activado) busca la FRASE EXACTA y, si no aparece, se amplía solo a OR avisándolo; en modo OR el número de páginas mide el corpus, no la pertinencia. Avanza con pagina.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textoYesTérminos a buscar, ej. "nulidad electoral", "liquidación del contrato"
exactoNoFrase exacta en SAMAI (activado); si no aparece, se amplía solo a OR con aviso. Ponlo en false para ampliar a propósito.
limiteNoCuántas mostrar de la página (hasta 10)
paginaNoPágina de resultados, desde 1. SAMAI pagina en bloques de ~10 y no admite un desplazamiento libre, por eso aquí se pide la página y no el "desde" del resto de herramientas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / properties / exacto / description
      Previous value: -"Buscar la frase exacta (entre comillas en el buscador SAMAI). Viene activado; si la frase no aparece en la página, se amplía solo a OR con un aviso. Ponlo en false para ampliar a propósito."New value: +"Frase exacta en SAMAI (activado); si no aparece, se amplía solo a OR con aviso. Ponlo en false para ampliar a propósito."
  2. Changed1 schema field changedv1.13.0
    • addedInput schema / properties / exacto
      Added value: +{
+  "default": true,
+  "description": "Buscar la frase exacta (entre comillas en el buscador SAMAI). Viene activado; si la frase no aparece en la página, se amplía solo a OR con un aviso. Ponlo en false para ampliar a propósito.",
+  "type": "boolean"
+}
  3. Changed3 schema fields changedv1.9.0
    • changedInput schema / properties / limite / description
      Previous value: -"El buscador entrega páginas de 9 como máximo"New value: +"Cuántas mostrar de la página (hasta 10)"
    • changedInput schema / properties / limite / maximum
      Previous value: -9New value: +10
    • addedInput schema / properties / pagina
      Added value: +{
+  "default": 1,
+  "description": "Página de resultados, desde 1. SAMAI pagina en bloques de ~10 y no admite un desplazamiento libre, por eso aquí se pide la página y no el \"desde\" del resto de herramientas.",
+  "minimum": 1,
+  "type": "integer"
+}
  4. First observedv1.6.0

TDQS

A4.3/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 well: it explains the exact-match-then-OR-fallback behavior with a notice, and warns that in OR mode the page count measures corpus size, not relevance. It also mentions each result includes the legal problem, its answer, and the SAMAI link. Missing: rate limits, auth, or what a failure/empty result looks like.

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-loads what the tool returns and its tribunal scope, then the search mechanics, then pagination. Dense but each sentence carries routing or behavioral information. Parenthetical enum-like listings add bulk but serve disambiguation.

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 search tool with no output schema and no annotations, the description covers scope, result shape (problema jurídico, respuesta, SAMAI link), and search-mode behavior. Remaining gaps are edge-case handling (empty results, timeouts) but nothing an agent strictly needs to invoke correctly.

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 baseline is 3, but the description adds value by explaining why 'pagina' exists (SAMAI paginates in ~10 blocks without free offset) and reinforcing the exacto OR fallback. The 'limite' nuance of per-page display is partly covered by the schema.

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 (buscar providencias del Consejo de Estado) and explicitly distinguishes the tribunal from the Corte Constitucional and the Suprema, which is essential given sibling tools like buscar_jurisprudencia_suprema. It also enumerates the subject matters (nulidad y restablecimiento, contratación estatal, nulidad electoral, reparación directa, conceptos de la Sala de Consulta).

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?

The 'tribunal DISTINTO de la Corte Constitucional y de la Suprema' clause gives clear when-to-use guidance by differentiating from sibling jurisprudence tools. It also explains how to advance results with 'pagina'. It does not name specific sibling tools or give explicit when-not-to-use conditions, but the tribunal distinction is a strong routing cue.

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