dgcp-mcp-server

Generador de borradores de oferta (Sobre A y B)

dgcp_generador_propuesta_sncc

Read-onlyIdempotent

Generates draft bid proposals for Dominican public tenders: cover letter, sworn no-disqualification declaration, economic offer with ITBIS, and file checklist. Adjusts guarantees for MIPYME bidders.

Instructions

Genera borradores de la carta de presentacion, la declaracion jurada de no estar en el regimen de inhabilidades (Arts. 38-39 Ley 47-25), la oferta economica con ITBIS y el checklist del expediente, con los datos reales del proceso. Ajusta las garantias y el anticipo si el oferente es MIPYME (Arts. 174-175 Ley 47-25). Usa siempre los formularios estandar que publica el pliego del proceso: esto es un borrador para completarlos.

Input Schema

Name	Required	Description
`rnc`	Yes
`rpe`	Yes
`es_mipyme`	No	true si el oferente es MIPYME certificada.
`aplica_itbis`	No	false si el bien o servicio esta exento de ITBIS (default true, 18%).
`razon_social`	Yes	Razon social del oferente.
`codigo_proceso`	Yes	Codigo oficial del proceso.
`descripcion_oferta`	No	Descripcion breve de lo ofertado.
`plazo_entrega_dias`	No	Plazo de entrega o ejecucion en dias calendario (default 15).
`representante_legal`	Yes
`cedula_representante`	Yes
`monto_ofertado_subtotal`	Yes	Subtotal de la oferta antes de ITBIS (DOP).

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv5.0.0Oct 17, 2026

addedInput schema / properties / aplica_itbis

Added value: +{
+  "description": "false si el bien o servicio esta exento de ITBIS (default true, 18%).",
+  "type": "boolean"
+}

removedInput schema / properties / cedula_representante / description
```
Removed value: -"Numero de cedula del representante legal."
```
addedInput schema / properties / cedula_representante / minLength
```
Added value: +3
```

changedInput schema / properties / codigo_proceso / description

Previous value: -"Codigo oficial del proceso en la DGCP (ej. 'INFOTEP-DAF-CM-2026-0080')."New value: +"Codigo oficial del proceso."

addedInput schema / properties / codigo_proceso / minLength
```
Added value: +3
```

addedInput schema / properties / descripcion_oferta

Added value: +{
+  "description": "Descripcion breve de lo ofertado.",
+  "type": "string"
+}

removedInput schema / properties / descripcion_servicio

Removed value: -{
-  "description": "Breve descripcion de los bienes, software o consultoria a ofertar.",
-  "type": "string"
-}

addedInput schema / properties / es_mipyme

Added value: +{
+  "description": "true si el oferente es MIPYME certificada.",
+  "type": "boolean"
+}

changedInput schema / properties / monto_ofertado_subtotal / description

Previous value: -"Monto subtotal de tu oferta economica antes de ITBIS en DOP."New value: +"Subtotal de la oferta antes de ITBIS (DOP)."

addedInput schema / properties / plazo_entrega_dias

Added value: +{
+  "description": "Plazo de entrega o ejecucion en dias calendario (default 15).",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / razon_social / description

Previous value: -"Nombre o razon social de tu empresa oferente."New value: +"Razon social del oferente."

addedInput schema / properties / razon_social / minLength
```
Added value: +2
```

removedInput schema / properties / representante_legal / description

Removed value: -"Nombre completo del representante legal o titular."

addedInput schema / properties / representante_legal / minLength
```
Added value: +3
```

removedInput schema / properties / rnc / description

Removed value: -"Numero de RNC o identificacion tributaria de tu empresa."

addedInput schema / properties / rnc / minLength
```
Added value: +3
```

removedInput schema / properties / rpe / description

Removed value: -"Numero de Registro de Proveedores del Estado (RPE)."

removedInput schema / properties / tiempo_entrega_dias

Removed value: -{
-  "default": 15,
-  "description": "Tiempo de entrega o ejecucion en dias calendario.",
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}

First observedv4.1.0Oct 2, 2026

TDQS

A3.9/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, open-world), so the bar is lower. The description still adds meaningful behavior: the output is explicitly a draft requiring completion on official pliego forms, and legal-article-conditional adjustments (Arts. 38-39, 174-175 Ley 47-25) are disclosed. It does not describe the output's format or whether anything is persisted, which keeps it from a 5.

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 tight sentences that lead with what gets generated, then the conditional MIPYME logic, then the draft caveat. The document enumeration is long but every item is load-bearing information about the output, so it stays dense rather than padded.

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 11-parameter, 7-required generator with no output schema, the description does the important work: it identifies which documents come back and warns that the result is an incomplete draft. What is missing is the shape of the return (plain text, file link, structured sections) and any note on how the optional ITBIS/MIPYME flags change the generated content.

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 coverage is 64% and the description names no parameters directly. It does implicitly map conceptual inputs onto two optional parameters (es_mipyme via the MIPYME adjustment clause, aplica_itbis via the ITBIS reference), and 'datos reales del proceso' gestures at codigo_proceso, but the remaining required fields like rnc, rpe and cedula_representante get no added meaning beyond the schema.

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 (genera borradores) and enumerates the exact artifacts produced: carta de presentación, declaración jurada de inhabilidades, oferta económica con ITBIS y checklist del expediente. This clearly separates it from every sibling, all of which are search/analysis tools rather than document generators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful context (a draft to be completed, built from real process data and the pliego's standard forms) and conditions the guarantee/advance calculations on MIPYME status. However, it never states when to reach for this tool versus alternatives such as dgcp_calculadora_legal or dgcp_simulador_puntuacion, and offers no exclusions or prerequisites, leaving route selection implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Generador de borradores de oferta (Sobre A y B)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools