Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar jurisprudencia de la Corte Suprema de Justicia

buscar_jurisprudencia_suprema

Search Colombian Supreme Court jurisprudence by chamber, year, or magistrate since 1991. Results include cited norms and paths to retrieve full documents.

Instructions

Providencias de la Corte Suprema por sala: Tutelas, Civil, Laboral o Penal, desde 1991. Complementa a buscar_jurisprudencia, que es de la Corte CONSTITUCIONAL: son tribunales distintos. Cada resultado trae las NORMAS QUE CITA (resolubles con resolver_cita) y una RUTA con la que obtener_documento con fuente="suprema" devuelve el texto. CÓMO BUSCA: sobre el texto completo y sin descartar palabras comunes, así que "de" devuelve 69.454 resultados; por eso busca la FRASE EXACTA por defecto. Usa términos distintivos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoAño de cuatro dígitos
salaNoSala de la Corte. Obligatoria: sin ella el buscador no responde.Tutelas
desdeNoCuántas saltarse antes de empezar
textoYesTérminos a buscar, ej. "despido sin justa causa"
exactoNoFrase exacta (activado). Con false el buscador une con OR: "despido sin justa causa" pasa de 20.233 a 176.012 providencias y en la sala Penal es inservible. Ponlo en false solo para ampliar a propósito.
limiteNoCuántas mostrar. El buscador entrega páginas de 10 como máximo; para ver más, usa desde.
magistradoNoNombre del magistrado ponente

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; viene activado. Con exacto=false el buscador une las palabras con OR y \"despido sin justa causa\" devuelve 176.012 providencias contra 20.233 con la frase: en la sala Penal ese modo llega a 33.607 resultados y es inservible. Ponlo en false solo para ampliar a propósito una búsqueda que quedó corta."New value: +"Frase exacta (activado). Con false el buscador une con OR: \"despido sin justa causa\" pasa de 20.233 a 176.012 providencias y en la sala Penal es inservible. Ponlo en false solo para ampliar a propósito."
  2. Changed2 schema fields changedv1.9.0
    • changedInput schema / properties / exacto / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / exacto / description
      Previous value: -"Buscar la frase exacta. MUY recomendable con frases: sin esto el buscador une las palabras con OR y \"despido sin justa causa\" devuelve 176.012 providencias contra 20.233 con exacto=true."New value: +"Buscar la frase exacta; viene activado. Con exacto=false el buscador une las palabras con OR y \"despido sin justa causa\" devuelve 176.012 providencias contra 20.233 con la frase: en la sala Penal ese modo llega a 33.607 resultados y es inservible. Ponlo en false solo para ampliar a propósito una búsqueda que quedó corta."
  3. First observedv1.6.0

TDQS

A4.1/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 discloses the search engine semantics (full-text, no stopword filtering, exact-phrase default), the consequence of exacto=false (result explosion, unusable in Penal), and the shape of each result (cited norms, a ruta). It omits any auth/permission or rate-limit notes, which is a minor gap for a public legal dataset.

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 resource and scope, then differentiation, then output, then search behavior. Every clause carries signal, though the paragraph is dense and long enough that the search-semantics detail could be trimmed.

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, so the description appropriately explains what each result contains (normas and a ruta for retrieval) and the search behavior of a 7-parameter tool. Combined with the 100%-covered schema, an agent has what it needs; only auth/limit context is absent.

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 the baseline is 3. The description restates the exacto behavior and notes sala's obligatoriness, but these are already documented in the schema fields, so it adds little parameter meaning beyond what the structured data provides.

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?

Starts with a specific verb+resource and coverage: 'Providencias de la Corte Suprema por sala: Tutelas, Civil, Laboral o Penal, desde 1991.' It explicitly disambiguates from the same-named sibling by naming the different tribunal (Corte Constitucional vs Corte Suprema), so an agent can route without opening either schema.

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?

Gives explicit routing context by naming buscar_jurisprudencia and explaining that these are distinct courts, plus follow-up chaining (resolver_cita for cited norms, obtener_documento with fuente="suprema" for full text). It lacks guidance against the other search siblings (e.g., buscar_por_tema), so it is clear but not exhaustive.

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