Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Explicar por qué una norma aplica a un subtema

explicar_relacion_tema

Explain why a Colombian norm is relevant to a specific subtopic by returning the matching restrictor excerpt from the Gestor Normativo.

Instructions

Devuelve el "restrictor": el extracto que explica por qué esa norma es pertinente para ESE subtema en concreto. Ambos identificadores deben salir de la MISMA fila de buscar_por_tema, y el temsubid va con su prefijo ("ts-38872"): un id de listar_catalogos (catalogo="subtemas") o de otros catálogos se rechaza aquí. Para ver todos los restrictores de una norma de una vez, usa obtener_documento con fuente="gestor" y mira su bloque "Temas asociados".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
normidYesnormid de la misma fila de buscar_por_tema
temsubidYestemsubid de buscar_por_tema, con su prefijo: "ts-38872"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.1
    • changedInput schema / required
      Previous value: -[
-  "normid"
-]New value: +[
+  "temsubid",
+  "normid"
+]
  2. Changed3 schema fields changedv1.9.0
    • changedInput schema / properties / temsubid / description
      Previous value: -"temsubid de buscar_por_tema (no vale el id de listar_subtemas)"New value: +"temsubid de buscar_por_tema, con su prefijo: \"ts-38872\""
    • removedInput schema / properties / temsubid / pattern
      Removed value: -"^\\d+$"
    • changedInput schema / required
      Previous value: -[
-  "temsubid",
-  "normid"
-]New value: +[
+  "normid"
+]
  3. First observedv1.6.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose meaningful validation behavior: it rejects temsubid values sourced from listar_catalogos or other catalogs. It also reveals the coupling requirement between the two ids. It stops short of describing output format or failure modes in depth, but covers the key behavioral constraint well.

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?

Three sentences, front-loaded with the return value before constraints and the alternative. Dense and largely waste-free, though the parenthetical prefix example and the alternative tool reference add some length.

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 two-parameter tool with no output schema or annotations, the description supplies the essential context: what it returns, where the ids come from, what gets rejected, and an alternative for bulk retrieval. It is close to complete, with only return structure left implicit.

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: it specifies the temsubid prefix format ("ts-38872") and, crucially, the cross-parameter constraint that both ids must originate from the same buscar_por_tema row, which the schema does not convey.

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: it returns the "restrictor", defined inline as the extract explaining why a norm is pertinent to a specific subtopic. This is clearly distinguishable from siblings like buscar_por_tema and obtener_documento, which it explicitly references.

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?

Explicit when-to-use: both identifiers must come from the SAME row of buscar_por_tema. It names the alternative (obtener_documento with fuente="gestor") and its purpose, and states an explicit exclusion (ids from listar_catalogos are rejected here).

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