Skip to main content
Glama
Sign In
Normativa Colombia MCP

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Explicar por qué una norma aplica a un subtema

explicar_relacion_tema
Read-onlyIdempotent

Get the excerpt that explains why a specific Colombian norm is relevant to a selected subtopic, using matching norm and subtopic IDs.

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

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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real context: it describes what is returned (the restrictor excerpt) and discloses validation behavior (ids not sourced from buscar_por_tema are rejected).

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 the return value, then constraints, then the alternative — a logical order. Dense but every sentence carries information; minor overlap between the prefix constraint and the schema description keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description explains the return value (the restrictor extract) and the sourcing/validation constraints. Nothing an agent needs in order to invoke it correctly is missing.

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. The description adds meaning beyond the schema by tying both ids to the same source row and stressing the required 'ts-' prefix, plus the consequence of passing a catalog id. This reinforces and extends the schema rather than merely repeating it.

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' excerpt explaining why a given norm applies to a specific subtopic. It distinguishes itself from siblings by name (buscar_por_tema, listar_catalogos, obtener_documento), so an agent can route without opening another schema.

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 states the prerequisite (both ids must come from the SAME row of buscar_por_tema), the when-not (an id from listar_catalogos or other catalogs is rejected here), and a clear alternative for a different need (obtener_documento with fuente='gestor' to see all restrictors at once).

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