Skip to main content
Glama
dgcp-mcp-server

dgcp-mcp-server

Calculadora normativa: umbrales 2026, modalidad, plazos y garantias

dgcp_calculadora_legal
Read-onlyIdempotent

Calculates Dominican procurement modality, minimum call period, and MIPYME guarantees from a budget, and flags if the chosen modality is below legal thresholds.

Instructions

Para un presupuesto dado calcula, con la Ley 47-25, el Dec. 52-26 y los umbrales 2026 (Resolucion PNP-03-2026):

  1. Modalidad que corresponde y plazo minimo de convocatoria (Art. 101).

  2. Si la modalidad usada por la institucion es inferior a la legal (indicio de fraccionamiento, Art. 81).

  3. Garantia de seriedad (1%), fiel cumplimiento (4% o 1% MIPYME), anticipo MIPYME (30%) y reglas especiales MIPYME.

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": {
      "monto_estimado": "<monto_estimado>"
    },
    "name": "dgcp_calculadora_legal"
  }
}

Input Schema

NameRequiredDescriptionDefault
es_mipymeNotrue si el oferente es MIPYME certificada.
tipo_objetoNoDefault 'bienes_servicios'.
monto_estimadoYesPresupuesto estimado en DOP.
modalidad_planteadaNoModalidad usada por la institucion, para verificar si es inferior a la legal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv5.0.0
    • removedInput schema / properties / es_mipyme / default
      Removed value: -false
    • changedInput schema / properties / es_mipyme / description
      Previous value: -"true si la empresa oferente cuenta con certificación MIPYME del MICM"New value: +"true si el oferente es MIPYME certificada."
    • changedInput schema / properties / modalidad_planteada / description
      Previous value: -"Modalidad utilizada por la institución para validar si es correcta o si incurre en fraccionamiento."New value: +"Modalidad usada por la institucion, para verificar si es inferior a la legal."
    • changedInput schema / properties / monto_estimado / description
      Previous value: -"Monto estimado del proceso en pesos dominicanos (DOP)."New value: +"Presupuesto estimado en DOP."
    • removedInput schema / properties / tipo_objeto / default
      Removed value: -"bienes_servicios"
    • changedInput schema / properties / tipo_objeto / description
      Previous value: -"Tipo de contratación: 'bienes_servicios' u 'obras'"New value: +"Default 'bienes_servicios'."
  2. First observedv4.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful beyond-annotation context: it names the exact legal sources and thresholds version (Resolución PNP-03-2026) and the specific article references (Art. 101, 81), so an agent knows which rulebook is applied. It doesn't describe output format or unit assumptions, keeping it below 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?

A single front-loaded sentence plus a compact numbered list of outputs — efficient and structured. Slightly dense with legal citations, but no wasted sentences.

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 read-only calculator with 4 well-covered params and no output schema, the description gives enough: it enumerates what will be computed and the legal basis. It stops short of describing return shape (fine, no output schema) and of usage routing, so not a 5.

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% (every param documented, enum on tipo_objeto), so the baseline is 3. The description references the budget input and the modality-verification logic, but adds no new meaning beyond what the schema already states for es_mipyme / modalidad_planteada.

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 computational action (calculate, based on Ley 47-25, Dec. 52-26 and 2026 thresholds) for a given budget, and enumerates the three concrete outputs (modality + minimum deadline, possible fractionalization, guarantee percentages). This clearly differentiates it from siblings like dgcp_simulador_puntuacion or dgcp_buscar_licitaciones.

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?

The inputs imply when it applies (you have a budget and want modality/plazo/garantías), but there is no explicit statement of when to use this vs. alternatives, no prerequisites, and no exclusions. Usage is only inferable from the listed outputs.

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