Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar normas en el Gestor Normativo

buscar_normas

Search Colombian public-sector laws, decrees, resolutions, concepts, and court rulings by keyword, entity, year, number, or topic to find relevant norms.

Instructions

Busca leyes, decretos, resoluciones, conceptos y sentencias del sector público colombiano. IMPORTANTE: el buscador del portal indexa solo los resúmenes temáticos, NO el articulado completo, y une los términos con OR. Usa pocas palabras y muy distintivas. Para buscar dentro del texto de una norma concreta, usa obtener_documento con fuente="gestor" y buscar_en_texto. Para una cita exacta, usa resolver_cita.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoAño de cuatro dígitos, como texto. Ej.: "2004"
temaNoNombre del tema, o su id de listar_catalogos con prefijo: "tema-24457"
limiteNo
numeroNoNúmero de la norma, como texto. Ej.: "909"
entidadNoNombre o id: "Corte Constitucional", "Congreso de la República"
subtemaNoid de listar_catalogos con catalogo="subtemas" y prefijo ("sub-38968"), o su nombre si además indicas tema. El "ts-" de buscar_por_tema no vale aquí.
palabrasNoTérminos distintivos; evita frases largas
tipo_documentoNoNombre o id del catálogo de tipos del Gestor: "Ley", "Decreto", "Resolución", "Concepto". Uno que no esté se rechaza con la lista, sin buscar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / properties / tipo_documento / description
      Previous value: -"Nombre o id: \"Ley\", \"Decreto\", \"Sentencia\", \"Concepto\""New value: +"Nombre o id del catálogo de tipos del Gestor: \"Ley\", \"Decreto\", \"Resolución\", \"Concepto\". Uno que no esté se rechaza con la lista, sin buscar"
  2. Changed1 schema field changedv1.11.2
    • changedInput schema / properties / subtema / description
      Previous value: -"id de listar_subtemas con prefijo (\"sub-38968\"), o su nombre si además indicas tema. El \"ts-\" de buscar_por_tema no vale aquí."New value: +"id de listar_catalogos con catalogo=\"subtemas\" y prefijo (\"sub-38968\"), o su nombre si además indicas tema. El \"ts-\" de buscar_por_tema no vale aquí."
  3. Changed2 schema fields changedv1.9.0
    • changedInput schema / properties / subtema / description
      Previous value: -"subtemaid de listar_subtemas, o su nombre si además indicas tema. NO sirve el temsubid de buscar_por_tema."New value: +"id de listar_subtemas con prefijo (\"sub-38968\"), o su nombre si además indicas tema. El \"ts-\" de buscar_por_tema no vale aquí."
    • changedInput schema / properties / tema / description
      Previous value: -"Nombre o id de tema del catálogo"New value: +"Nombre del tema, o su id de listar_catalogos con prefijo: \"tema-24457\""
  4. First observedv1.6.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses critical search behavior: the portal indexes only thematic summaries, not full articulado, and joins terms with OR. It does not cover auth, rate limits, or return format, but the key limitations are stated.

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?

The description is front-loaded with purpose and the critical indexing caveat before alternatives. Four sentences, no waste, and the most important limitation is marked clearly with IMPORTANTE.

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 an 8-parameter search tool with no output schema and no annotations, the description covers scope, indexing limitation, query behavior, and two alternatives. It could mention return format or pagination, but the core invocation guidance is complete enough.

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 description coverage is 88%, so the baseline would be 3. The description adds meaningful semantics for the main query parameter by explaining OR-joining and advising few distinctive terms, which goes beyond the schema descriptions. It does not explain every filter, but it exceeds the baseline.

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: busca leyes, decretos, resoluciones, conceptos y sentencias del sector público colombiano. It distinguishes this tool from two siblings by directing full-text search to obtener_documento and exact citations to resolver_cita.

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?

Explicitly tells the agent when to use this tool versus alternatives: use obtener_documento for text inside a specific norm, and resolver_cita for an exact citation. It also gives concrete query advice for the free-text search: use few, highly distinctive words.

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