Skip to main content
Glama
edwin042331-hue

dgcp-mcp-server

by edwin042331-hue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar licitaciones y procesos de compra (DGCP)

dgcp_buscar_licitaciones
Read-onlyIdempotent

Search Dominican Republic public procurement tenders by keyword, institution, status, modality, budget, or MIPYME category, and get closing dates and portal links.

Instructions

Busca procesos de compra publica del Estado dominicano. Campos VERIFICADOS contra la API real.

IMPORTANTE - como funciona la API:

  • La API NO filtra del lado del servidor. Siempre devuelve los procesos mas recientes primero.

  • Esta herramienta descarga varias paginas (parametro 'paginas', default 5 = 500 procesos) y filtra localmente.

  • Un termino generico deja fuera resultados. Para un tema, haz VARIAS llamadas con terminos distintos (ej. tecnologia: software, licencia, computadora, laptop, servidor, redes, impresora, sistema) y une los resultados.

Estado:

  • 'abierto' = estado "Proceso publicado" Y fecha de cierre aun futura. Es lo que se quiere el 90% de las veces.

  • 'publicado' = estado publicado sin importar la fecha

  • 'adjudicado' = ya tiene ganador

  • 'apertura' = sobres abiertos

  • 'cerrado' = etapa cerrada

  • 'todos' = sin filtrar

Devuelve: codigo, institucion, estado, modalidad, monto, fecha de cierre con dias restantes, MIPYME y enlace al portal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
estadoNo'abierto' = publicado Y con fecha de cierre futura (lo que casi siempre se quiere)
limiteNoCuantos resultados devolver (default 10)
mipymeNoSolo procesos dirigidos a MIPYMES
paginasNoCuantas paginas de la API escanear (default 5, 100 procesos c/u)
terminoNoTexto a buscar en titulo y descripcion. Ej: 'software', 'laptop', 'servidor'
modalidadNoTexto de la modalidad. Ej: 'Licitacion Publica', 'Compras Menores'
monto_maxNoMonto maximo estimado en DOP
monto_minNoMonto minimo estimado en DOP
institucionNoNombre (o parte) de la institucion. Ej: 'Impuestos Internos', 'Educacion'
mipyme_mujerNoSolo procesos dirigidos a MIPYMES de mujeres

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial non-obvious behavior: client-side filtering, multi-page scanning controlled by 'paginas' (default 5 = 500 processes), and most-recent-first ordering. This is exactly the kind of context that prevents misuse.

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?

Well front-loaded with headers and bulleted state definitions; no filler. It is on the longer side, but the length is justified by a 10-parameter tool with nuanced API behavior.

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?

For a tool with no output schema, the description usefully enumerates returned fields (codigo, institucion, estado, modalidad, monto, fecha de cierre, MIPYME, enlace), and all parameters are documented in the schema. An agent has what it needs to call it correctly.

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 semantics beyond the schema: the precise meaning of 'abierto' (published AND future closing date), the generic-term pitfall for 'termino', and the default page size. It exceeds what the structured fields alone 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 ('Busca') and resource ('procesos de compra publica del Estado dominicano'), and it is clearly distinguishable from siblings like dgcp_buscar_contratos or dgcp_buscar_proveedores. The title reinforces the scope without ambiguity.

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 strong operational guidance: the API does not filter server-side, generic terms drop results, and recommends multiple calls with varied terms per topic. It also flags that 'abierto' is the desired state ~90% of the time. It stops short of explicitly routing the agent to sibling tools for related queries.

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