Tu agente de IA trabaja tus bases de datos

Qué le pedirías a tu agente

• “Mostrame qué tablas tiene la base de producción y cómo se relacionan”
• “Contá cuántos pedidos entraron ayer y agrupalos por estado”
• “Agregá una columna de fecha de baja a la tabla de clientes”
• “Esta consulta va lenta: explicame el plan y decime qué índice falta”

Las herramientas de este dominio (15)

Salen del propio servidor MCP en cada compilación. Las descripciones están en inglés porque son las que lee el agente.

Cloud – Databases

• actualizar_fila_db_vps: Updates ONE row, identified by its COMPLETE primary key. There is no bulk update on purpose: an UPDATE with a wrong WHERE is one of the few things here that cannot be undone.
• borrar_fila_db_vps: Deletes ONE row by complete primary key. Same rule as the update: one row at a time.
• consultar_sql_db_vps: Runs a READ-ONLY SQL query, one single statement. Writes are rejected here on purpose: use the row tools or ejecutar_ddl_db_vps. Pass values through `params`, never glued into the SQL text. (solo lectura)
• contar_filas_db_vps: Exact COUNT(*), with the same filter as leer_filas_db_vps. It is a separate tool because on a big table it costs far more than reading a page. (solo lectura)
• describir_tabla_db_vps: Columns (with a normalized type that is the same for both engines), nullability, primary key, foreign keys and indexes. Read this before writing rows: it is where the real column names come from. (solo lectura)
• ejecutar_ddl_db_vps: Runs ONE DDL statement (CREATE / ALTER / DROP / TRUNCATE ...). If it DESTROYS data it fails with HTTP 428 and tells you `confirmacion_esperada`: the exact name of the object. Retry passing it in `confirmacion`. Do not…
• explicar_sql_db_vps: EXPLAIN of a query, in each engine's own format (they are not comparable, and forcing a common shape would make both useless). analizar=True runs EXPLAIN ANALYZE, which DOES execute the query — PostgreSQL only. (solo lectura)
• guardar_credencial_db_vps: Stores the engine credentials when the client changed them by hand (the default password is the VPS slug). Encrypted at rest and NEVER returned: no tool reads it back.
• historial_operaciones_db_vps: The log of destructive operations run against this VPS's databases: who, when, which statement, on which object, and whether it came from the web interface or from an agent. (solo lectura)
• insertar_fila_db_vps: Inserts ONE row. `valores` is {column: value}; columns are validated against the catalog and values travel as driver placeholders. Returns the row as it ended up, with defaults and auto-increment already resolved.
• leer_filas_db_vps: One page of rows, WITHOUT writing SQL. `filtro` uses a whitelist of operators, `orden` takes column names with an optional '-' prefix. For the next page pass `despues_de` = the `siguiente` of the previous answer (keyset… (solo lectura)
• listar_bases_db_vps: Lists the databases of an engine, with size and encoding. (solo lectura)
• listar_motores_db_vps: Lists the database engines installed on a VPS (PostgreSQL, MySQL/MariaDB), their port, version and whether they are running. sondear=False answers from cache without touching the VPS. (solo lectura)
• listar_tablas_db_vps: Lists tables and views of a database, with an estimated row count (free: it comes from the engine's own statistics, it does not run COUNT(*)). (solo lectura)
• probar_conexion_db_vps: Checks that the backend can actually reach that engine on the VPS and log in. Use this first when something fails: it tells apart 'the VPS is off', 'the engine is down' and 'the password was changed by hand'. (solo lectura)

Lo mismo, desde el panel

• PostgreSQL
• MySQL
• Gestor de bases de datos