MCP Suppliers — contrato de tools (US 61)¶

Servidor: services/mcp-suppliers-server
Transports: stdio (local) · HTTP POST/GET /mcp (Streamable, para ACA/Foundry)

validate_supplier¶

Description: Validate supplier exists and status is Active.

Input

Field	Type	Required
taxId	string	one of taxId / supplierId
supplierId	string	one of taxId / supplierId

Output

{
  "result": "VALID",
  "reason": "Supplier is active",
  "supplier": {
    "supplierId": "SUP-1001",
    "name": "Acme Supplies SAS",
    "taxId": "900123456",
    "status": "Active",
    "riskLevel": "Low"
  }
}

INVALID when missing, not found, or not Active (includes supplier payload when found but inactive).

get_supplier¶

Lookup without Active gate — demo/debug.

Alignment¶

Same seed IDs as finance-api / data/sample/finance.
Finance process still runs deterministic FIN-001; the Agent will call this MCP tool for explanations / tool-calling demos (E4).

Deploy en Azure (pipeline-only)¶

Paso	Pipeline	Resultado
1	eai-terraform-dev (apply en `deployment`)	CA `ca-eai-mcp-sup-dev` + env SQL/MI
2	eai-mcp-suppliers-deploy	ACR `eai-mcp-suppliers:dev` + roll imagen

Health: https://<mcp-fqdn>/api/platform/health
MCP HTTP: https://<mcp-fqdn>/mcp

Si el build corre antes del apply, el stage Deploy avisa y sale OK; re-ejecutar el deploy tras crear la CA.