Skip to main content
Glama
Yonsn76

MyPos MCP

by Yonsn76

eliminarColumna

Remove a column from a database table after explicit confirmation. This action permanently deletes all data in the column and requires exact phrase verification to proceed.

Instructions

Sigue estas reglas OBLIGATORIAS para eliminar una columna: ADVERTENCIA INICIAL: Informa al usuario que eliminar una columna es una acción DESTRUCTIVA y PERMANENTE que borrará todos los datos que contiene. CONFIRMACIÓN EXPLÍCITA: Para proceder, el usuario DEBE escribir la frase exacta: "Confirmar eliminación de la columna [nombreColumna] de la tabla [nombreTabla]". VERIFICACIÓN ESTRICTA: No ejecutes la eliminación si la frase de confirmación no es una coincidencia exacta. USO EXCLUSIVO: Úsala solo para eliminar columnas, no tablas ni registros. EJEMPLO: "Elimina la columna edad de la tabla clientes."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
columnaYesNombre de la columna a eliminar
tablaYesNombre de la tabla

Implementation Reference

  • The main handler function for the 'eliminarColumna' tool. Validates inputs, executes the ALTER TABLE DROP COLUMN SQL query using query_runner, and returns success or error response.
    async ({ tabla, columna }) => {
      try {
        if (!tabla || !columna) {
          return { isError: true, content: [{ type: 'text', text: 'Debes proporcionar la tabla y la columna.' }] };
        }
        await query_runner.runQuery(`ALTER TABLE ${quoteIdent(tabla)} DROP COLUMN ${quoteIdent(columna)}`);
        return { content: [{ type: 'text', text: `Columna '${columna}' eliminada de la tabla '${tabla}' exitosamente.` }] };
      } catch (e) {
        return { isError: true, content: [{ type: 'text', text: 'Error al eliminar la columna: ' + (e.message || e) }] };
      }
    }
  • Zod schema defining the input parameters: tabla (table name) and columna (column name).
    {
      tabla: z.string().describe('Nombre de la tabla'),
      columna: z.string().describe('Nombre de la columna a eliminar'),
    },
  • mcp_server.js:564-587 (registration)
    Complete registration of the 'eliminarColumna' tool on the MCP server, including name, detailed usage instructions, input schema, and inline handler function.
    server.tool(
      'eliminarColumna',
      'Sigue estas reglas OBLIGATORIAS para eliminar una columna:\n'
      + 'ADVERTENCIA INICIAL: Informa al usuario que eliminar una columna es una acción DESTRUCTIVA y PERMANENTE que borrará todos los datos que contiene.\n'
      + 'CONFIRMACIÓN EXPLÍCITA: Para proceder, el usuario DEBE escribir la frase exacta: "Confirmar eliminación de la columna [nombreColumna] de la tabla [nombreTabla]".\n'
      + 'VERIFICACIÓN ESTRICTA: No ejecutes la eliminación si la frase de confirmación no es una coincidencia exacta.\n'
      + 'USO EXCLUSIVO: Úsala solo para eliminar columnas, no tablas ni registros.\n'
      + 'EJEMPLO: "Elimina la columna edad de la tabla clientes."',
      {
        tabla: z.string().describe('Nombre de la tabla'),
        columna: z.string().describe('Nombre de la columna a eliminar'),
      },
      async ({ tabla, columna }) => {
        try {
          if (!tabla || !columna) {
            return { isError: true, content: [{ type: 'text', text: 'Debes proporcionar la tabla y la columna.' }] };
          }
          await query_runner.runQuery(`ALTER TABLE ${quoteIdent(tabla)} DROP COLUMN ${quoteIdent(columna)}`);
          return { content: [{ type: 'text', text: `Columna '${columna}' eliminada de la tabla '${tabla}' exitosamente.` }] };
        } catch (e) {
          return { isError: true, content: [{ type: 'text', text: 'Error al eliminar la columna: ' + (e.message || e) }] };
        }
      }
    );
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly describes destructive and permanent nature ('acción DESTRUCTIVA y PERMANENTE'), mandatory confirmation requirements ('CONFIRMACIÓN EXPLÍCITA'), strict verification rules ('VERIFICACIÓN ESTRICTA'), and provides a concrete example. This goes well beyond what the input schema provides about parameters.

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?

The description is well-structured with clear sections (ADVERTENCIA INICIAL, CONFIRMACIÓN EXPLÍCITA, etc.) and every sentence serves a purpose. It could be slightly more concise by combining some points, but the information density is high and front-loaded with critical warnings.

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

Completeness5/5

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

For a destructive tool with no annotations and no output schema, the description provides comprehensive context: it explains the destructive nature, specifies exact confirmation requirements, gives usage boundaries vs sibling tools, and includes an example. This adequately compensates for the lack of structured metadata about this high-risk operation.

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%, with both parameters clearly documented in the schema ('columna: Nombre de la columna a eliminar', 'tabla: Nombre de la tabla'). The description doesn't add significant parameter semantics beyond what's in the schema, though it reinforces parameter usage through the example. Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description explicitly states the tool's purpose as 'eliminar una columna' (delete a column), specifying both the verb (eliminar) and resource (columna). It clearly distinguishes this from sibling tools like eliminarTabla (delete table) by stating 'USO EXCLUSIVO: Úsala solo para eliminar columnas, no tablas ni registros' (EXCLUSIVE USE: Use it only to delete columns, not tables or records).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool vs alternatives: 'Úsala solo para eliminar columnas, no tablas ni registros' (Use it only to delete columns, not tables or records), directly contrasting with sibling tools like eliminarTabla. It also specifies prerequisites: the user must provide an exact confirmation phrase, making usage conditions clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yonsn76/MyPos-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server