bogamatic-sac-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAC_PASSWORD | Yes | Your password for the SAC system | |
| SAC_USERNAME | Yes | Your matricula (username) for the SAC system |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_novedades_cedulasA | Get the list of electronic cedula notifications (novedades). Each cedula is marked as 'NEW' or 'SEEN'. New cedulas are those not previously fetched. All fetched cedulas are stored to avoid duplicate notifications. |
| get_detalle_cedulaA | Get the full detail of a specific cedula notification. Returns: matricula, destinatario, dependencia, numeroExpediente, caratula, fecha (dd/MM/yyyy), tipoOperacion, idOperacion, textoOperacion (converted to Markdown), protocolo, and adjuntos[] (each with idFichero, nombre, datosExtra). |
| get_resumen_cedulaA | Get a complete summary of a cedula in a single call. Combines get_detalle_cedula + calcular_plazo into one response. Returns: destinatario, numeroExpediente, caratula, dependencia, fecha, tipoOperacion, idOperacion, textoOperacion (Markdown), adjuntos[] (each with idFichero, nombre, datosExtra), protocolo, and plazo (with fechaInicio, fechaPlazo, diasHabilesContados, diasSaltados). Use this instead of calling get_detalle_cedula and calcular_plazo separately. |
| get_expedienteA | Look up a single expediente (case) by its numeroExpediente OR idExpediente. Use this at the start of any chat about a case — it returns the full expediente record plus a |
| get_expedientesA | Search legal expedientes (cases/files) belonging to the authenticated lawyer. Supports fuzzy search on 'caratula'. Partial names are valid. If the user provides an expediente number, prefer using 'numeroExpediente' as the primary filter because it uniquely identifies the expediente. |
| get_novedades_expedientesA | Get expedientes (cases) that had activity in the last 7 days. Returns case number, title, court, status, and location. |
| get_operaciones_expedienteA | Get all operations (movements) for a specific expediente. Each operation returns: fecha (dd/MM/yyyy), tipoOperacion, idOperacion (prefixed E:/O: — pass through as-is to other tools), adjunto (boolean), firmada, presentadoPor, ubicacion, estado, and a flattened extras dict. |
| get_adjuntos_expedienteA | Get all attachments for an expediente. Each item returns: idFichero, idOperacion (prefixed E:/O: — pass through as-is to other tools), nombre (file name), fecha (dd/MM/yyyy), tipoOperacion, clasificacion, observaciones. Use idFichero, idOperacion and nombre as inputs for download_adjunto. |
| get_texto_operacion_expedienteA | Get the text content of an operation within an expediente as Markdown. Pass the idOperacion (with its E:/O: prefix) exactly as returned by get_operaciones_expediente or get_adjuntos_expediente. |
| download_adjuntoA | Download an attachment locally. Works for both cedulas (get_detalle_cedula adjuntos[]) and expediente operations (get_adjuntos_expediente). The destination is chosen by: (1) the first file:// root from the MCP client (e.g. Cowork project dir or Claude Code project dir), (2) the SAC_DOWNLOAD_DIR env var, or (3) ~/Downloads/bogamatic-sac/. The file is named {numeroExpediente}{fechaOperacion}{fileName}. |
| calcular_plazoA | Given a notification date (typically from a cedula), calculates the first day a procedural deadline begins to run. Cordoba's (Argentina) procedural law grants 3 grace days after notification before any deadline starts. This tool counts 3 business days forward (skipping weekends and court holidays) and returns the date when the deadline period actually begins. |
| send_whatsapp_notificationA | Send a WhatsApp notification about a cedula. The recipient phone number is resolved automatically from the authenticated user's account. The cedula details (destinatario, fecha, tipoOperacion, numeroExpediente, caratula) are loaded server-side from idCedula — the same ID used by get_resumen_cedula. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but there is some overlap between get_detalle_cedula and get_resumen_cedula, with the latter explicitly combining the former with calcular_plazo. This could cause misselection, though descriptions help. Similarly, get_operaciones_expediente and get_texto_operacion_expediente are complementary but distinct.
All tool names follow a consistent snake_case verb_noun pattern, with 'get_' for retrieval, 'download_', 'calcular_', and 'send_' for actions. The singular/plural use (cedula/cedulas, expediente/expedientes) is logical and predictable. No mixed naming conventions are present.
With 12 tools, the server is well-scoped for its domain of legal case management and notifications. Each tool addresses a specific need, and the count is within the ideal range for a focused MCP server. No redundant or unnecessary tools are apparent.
The tool surface covers the primary workflows: listing and reading cedulas, searching and viewing expedientes, retrieving operations and attachments, downloading files, calculating deadlines, and sending notifications. Minor gaps exist, such as lacking a way to filter attachments by operation or explicitly marking a cedula as seen, but these are workable or handled automatically.