Skip to main content
Glama
dgcp-mcp-server

dgcp-mcp-server

Generador de recurso administrativo (Ley 47-25)

dgcp_generador_recurso_impugnacion
Read-onlyIdempotent

Drafts procurement challenge filings under Ley 47-25, selects reconsideration or hierarchical appeal, calculates deadlines from notification dates, and adds precautionary measures.

Instructions

Redacta el recurso correcto segun la Ley 47-25:

  • Reconsideracion: primero y obligatorio, ante el organo responsable del proceso, en 10 dias habiles (Arts. 204-205).

  • Jerarquico impropio: contra la decision de la reconsideracion, ante la DGCP, en 10 dias habiles (Arts. 207-208).

  • Medida cautelar: instancia separada ante la DGCP mientras el recurso este pendiente (Art. 211); los recursos NO suspenden el acto por si solos (Art. 201). Calcula el vencimiento del plazo si se indica la fecha de notificacion. Si el proceso fue convocado bajo la Ley 340-06, lo advierte.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "codigo_proceso": "<codigo_proceso>",
      "acto_impugnado": "<acto_impugnado>",
      "hechos": "<hechos>",
      "empresa_recurrente": "<empresa_recurrente>",
      "rnc_recurrente": "<rnc_recurrente>",
      "representante": "<representante>"
    },
    "name": "dgcp_generador_recurso_impugnacion"
  }
}

Input Schema

NameRequiredDescriptionDefault
hechosYesRelato breve de lo ocurrido y por que perjudica al recurrente.
agraviosNoNormas o principios violados, si se conocen.
tipo_recursoNo'reconsideracion' (default): primer recurso, ante la institucion (Art. 204). 'jerarquico_impropio': contra la decision de la reconsideracion, ante la DGCP (Art. 207).
representanteYesRepresentante legal.
acto_impugnadoYesActo que se impugna: 'Acta de adjudicacion No. X', 'Informe de evaluacion', 'Pliego de condiciones'...
codigo_procesoYesCodigo del proceso.
rnc_recurrenteYes
rpe_recurrenteNo
empresa_recurrenteYes
fecha_notificacionNoFecha (YYYY-MM-DD) en que se notifico o publico el acto: calcula el vencimiento del plazo.
incluir_medida_cautelarNotrue = agrega la instancia separada de medida cautelar ante la DGCP (Art. 211).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv5.0.0
    • removedInput schema / properties / acto_atacado
      Removed value: -{
      -  "description": "Acto que se impugna (ej. 'Acta de Adjudicación No. XX', 'Pliego de Condiciones', 'Acta de Descalificación Técnica').",
      -  "type": "string"
      -}
    • addedInput schema / properties / acto_impugnado
      Added value: +{
      +  "description": "Acto que se impugna: 'Acta de adjudicacion No. X', 'Informe de evaluacion', 'Pliego de condiciones'...",
      +  "minLength": 3,
      +  "type": "string"
      +}
    • addedInput schema / properties / agravios
      Added value: +{
      +  "description": "Normas o principios violados, si se conocen.",
      +  "type": "string"
      +}
    • changedInput schema / properties / codigo_proceso / description
      Previous value: -"Codigo oficial del proceso licitado."New value: +"Codigo del proceso."
    • addedInput schema / properties / codigo_proceso / minLength
      Added value: +3
    • removedInput schema / properties / empresa_recurrente / description
      Removed value: -"Nombre de tu empresa que somete el recurso."
    • addedInput schema / properties / empresa_recurrente / minLength
      Added value: +2
    • addedInput schema / properties / fecha_notificacion
      Added value: +{
      +  "description": "Fecha (YYYY-MM-DD) en que se notifico o publico el acto: calcula el vencimiento del plazo.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / hechos
      Added value: +{
      +  "description": "Relato breve de lo ocurrido y por que perjudica al recurrente.",
      +  "minLength": 10,
      +  "type": "string"
      +}
    • addedInput schema / properties / incluir_medida_cautelar
      Added value: +{
      +  "description": "true = agrega la instancia separada de medida cautelar ante la DGCP (Art. 211).",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / motivo_agravio
      Removed value: -{
      -  "description": "Causal de violación (ej. 'Descalificación arbitraria habiendo cumplido ficha técnica', 'Adjudicación a empresa con precio superior sin justificación', 'Colusión demostrada entre oferentes').",
      -  "type": "string"
      -}
    • changedInput schema / properties / representante / description
      Previous value: -"Nombre del representante legal."New value: +"Representante legal."
    • addedInput schema / properties / representante / minLength
      Added value: +3
    • removedInput schema / properties / rnc_recurrente / description
      Removed value: -"RNC de tu empresa."
    • addedInput schema / properties / rnc_recurrente / minLength
      Added value: +3
    • addedInput schema / properties / rpe_recurrente
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tipo_recurso
      Added value: +{
      +  "description": "'reconsideracion' (default): primer recurso, ante la institucion (Art. 204). 'jerarquico_impropio': contra la decision de la reconsideracion, ante la DGCP (Art. 207).",
      +  "enum": [
      +    "reconsideracion",
      +    "jerarquico_impropio"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "codigo_proceso",
      -  "acto_atacado",
      -  "motivo_agravio",
      -  "empresa_recurrente",
      -  "rnc_recurrente",
      -  "representante"
      -]New value: +[
      +  "codigo_proceso",
      +  "acto_impugnado",
      +  "hechos",
      +  "empresa_recurrente",
      +  "rnc_recurrente",
      +  "representante"
      +]
  2. First observedv4.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations mark it readOnly/idempotent/non-destructive, consistent with a drafting/calculation tool. The description adds real depth beyond annotations: deadline computation (10 dias habiles per Arts. 204-205/207-208), the warning that recursos do not suspend the act (Art. 201), and the Ley 340-06 notice behavior. However it doesn't clarify output format or whether missing fecha_notificacion yields an error or skipped calculation.

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?

Front-loaded single verb phrase followed by a tight bulleted breakdown of the three recourses with articles and deadlines. Every bullet earns its place by adding legal specifics an agent would need; 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?

For a drafting tool with 11 params, 6 required, no output schema and no return-value info, the description is quite complete on legal behavior. Remaining gaps: no explanation of what documento is produced or how output is structured, which matters since there is no output schema.

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 73%, and the schema already documents key params (tipo_recurso enum, fecha_notificacion pattern, incluir_medida_cautelar, hechos, agravios). The description reinforces the tipo_recurso semantics and the fecha_notificacion deadline use, but adds no new meaning for the undocumented params (rpe_recurrente, rnc_recurrente). Baseline 3 fits.

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 (Redacta/redacta el recurso) and resource (recurso administrativo bajo Ley 47-25), and distinguishes the three recourse types with their scope and governing articles. Clearly differentiated from sibling tools like dgcp_calculadora_legal or dgcp_generador_propuesta_sncc.

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?

Explains each recourse type's sequence (reconsideracion primero y obligatorio, jerarquico impropio contra su decision, medida cautelar como instancia separada) and deadlines, giving a clear map of when each applies. Lacks an explicit 'do not use this when...' exclusion, but the sequencing is strongly implied.

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