Skip to main content
Glama
Angelthebestone

Normativa Colombia MCP

by Angelthebestone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Consultar un perfil sectorial preconfigurado

consultar_perfil

Query Colombian legal norms with preconfigured filters for a sector profile (labor, tax, environmental, public contracting, or energy) and get results plus the profile's sector and scope warning.

Instructions

Ejecuta la consulta con las fuentes y los filtros preconfigurados de un perfil sectorial (laboral, tributario, ambiental, contratación estatal o energía) y devuelve los resultados con el sector y la advertencia del perfil, que es lo que declara sus límites. NO uses un perfil para lo que no cubre: si la materia es otra, usa buscar_normas o resolver_cita.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textoYesConsulta dentro del perfil, ej. "teletrabajo"
limiteNoCuántos resultados devolver (máximo 20; por defecto 10)
perfilYesId del perfil, de describir_fuentes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.0
    • changedInput schema / properties / perfil / description
      Previous value: -"Id del perfil: laboral, tributario, ambiental, contratacion_estatal, energia"New value: +"Id del perfil, de describir_fuentes"
    • addedInput schema / properties / perfil / enum
      Added value: +[
+  "laboral",
+  "tributario",
+  "ambiental",
+  "contratacion_estatal",
+  "energia"
+]
  2. Changed1 schema field changedv1.10.2
    • addedInput schema / properties / limite / description
      Added value: +"Cuántos resultados devolver (máximo 20; por defecto 10)"
  3. Addedv1.10.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It adds useful behavior (results include the sector and an 'advertencia' that declares the profile's limits) and a scoping constraint, but says nothing about permissions, pagination, or mutation/read semantics.

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?

Two tight sentences with the core action front-loaded and the usage guardrail immediately after; every clause earns its place with no filler.

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?

With no output schema and no annotations, the description covers purpose, the routing rule, and partially what the call returns (sector + advertencia). It is nearly complete for a 3-parameter read tool, though richer return/error behavior would push it higher.

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 texto, limite and perfil are already documented, including the enum and the 1-20 range. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 ('Ejecuta la consulta') plus the resource (fuentes y filtros preconfigurados de un perfil sectorial) and even enumerates the five sector values. An agent can distinguish it from the many buscar_* siblings without opening any 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 gives the when-not condition ('NO uses un perfil para lo que no cubre: si la materia es otra') and names the concrete alternatives, buscar_normas and resolver_cita. This is a textbook routing instruction.

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