Skip to main content
Glama
Sign In
dgcp-mcp-server

dgcp-mcp-server

by edwin042331-hue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Buscar proveedores del Estado / RPE (DGCP)

dgcp_buscar_proveedores
Read-onlyIdempotent

Retrieve official supplier records from the Dominican Republic's procurement registry by RPE, RNC/cedula, or company name, including status and debarment alerts.

Instructions

Ficha oficial en el Registro de Proveedores del Estado: RPE, RNC, estado, MIPYME/MICM, rubro, ubicacion, contacto y constancia. Busca por RPE o RNC/cedula de forma exacta en el servidor. Por nombre, identifica la empresa a traves de su actividad reciente en contratos y ofertas. Avisa si el proveedor figura en la lista oficial de inhabilitados o suspendidos.

Input Schema

NameRequiredDescriptionDefault
rncNoRNC o cedula (exacto).
rpeNoNumero de RPE (exacto).
estadoNoEstado en el RPE: Activo, Suspendido, Cancelado, Desactualizado...
limiteNo
terminoNoRPE, RNC/cedula o nombre de la empresa. Los numeros se buscan de forma exacta.
provinciaNoProvincia, ej. 'SANTIAGO' (filtro de servidor; requiere tambien estado).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv5.0.0
    • changedInput schema / properties / estado / description
      Previous value: -"Estado en el RPE (ej. 'Activo', 'Inactivo')."New value: +"Estado en el RPE: Activo, Suspendido, Cancelado, Desactualizado..."
    • removedInput schema / properties / limite / description
      Removed value: -"Cuantos resultados devolver (default 10)"
    • removedInput schema / properties / mipyme
      Removed value: -{
-  "description": "true = solo proveedores clasificados como MIPYME.",
-  "type": "boolean"
-}
    • removedInput schema / properties / paginas
      Removed value: -{
-  "description": "Cuantas paginas de la API escanear (default 5, 100 proveedores c/u)",
-  "maximum": 20,
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / provincia / description
      Previous value: -"Provincia del proveedor (ej. 'Distrito Nacional', 'Santiago', etc.)."New value: +"Provincia, ej. 'SANTIAGO' (filtro de servidor; requiere tambien estado)."
    • changedInput schema / properties / rnc / description
      Previous value: -"Numero de RNC o identificacion del proveedor (numero_documento)."New value: +"RNC o cedula (exacto)."
    • changedInput schema / properties / rpe / description
      Previous value: -"Numero de Registro de Proveedores del Estado (RPE)."New value: +"Numero de RPE (exacto)."
    • removedInput schema / properties / rubro
      Removed value: -{
-  "description": "Rubro que provee: 'Bienes', 'Servicios', 'Obras'.",
-  "type": "string"
-}
    • changedInput schema / properties / termino / description
      Previous value: -"Texto a buscar en razon social, RNC, contacto, direccion o correo."New value: +"RPE, RNC/cedula o nombre de la empresa. Los numeros se buscan de forma exacta."
  2. First observedv4.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds real behavioral context: exact server-side matching for identifiers, name lookup inferred from recent contracts and bids, and a flag for officially disqualified or suspended suppliers. It omits pagination/limit behavior, but that is a minor gap given the annotation coverage.

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 sentences, front-loaded with the record contents, then search mechanics, then the disqualification warning. Mostly efficient, though the opening field enumeration is somewhat list-like and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, zero-required lookup with no output schema, the description usefully describes returned fields and search modes. However, it never explains how to call the tool when no identifier is supplied or how multiple matches are handled, leaving a real gap for a tool with all-optional parameters.

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 83%, so the schema already documents most parameters (rnc, rpe, estado, termino, provincia). The description adds the server-side exact-match semantics for numeric lookups and the name-resolution heuristic, but says nothing about 'limite' or the provincia-requires-estado constraint. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Buscar proveedores' in the Registro de Proveedores del Estado) and enumerates the fields returned (RPE, RNC, estado, MIPYME/MICM, rubro, ubicacion, contacto, constancia). It is clearly a registry lookup, but it never distinguishes itself from the sibling dgcp_radiografia_proveedor, which also profiles suppliers.

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?

Explains the two search modes (exact RPE/RNC on the server vs. name resolved through recent contract/bid activity), which implies usage but not when to prefer this tool over dgcp_radiografia_proveedor or other supplier-oriented siblings. No exclusions or prerequisites are given.

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