Skip to main content
Glama
vespo92

OPNSense MCP Server

haproxy_frontend_delete

Remove an HAProxy frontend by specifying its UUID to streamline configuration updates on OPNSense firewalls managed via the MCP server.

Instructions

Delete an HAProxy frontend

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesFrontend UUID

Implementation Reference

  • The `deleteFrontend` method in HAProxyResource class executes the core logic for the haproxy_frontend_delete tool: it sends a POST request to `/haproxy/settings/delFrontend/${uuid}` to delete the frontend and then calls reconfigure to apply changes.
    async deleteFrontend(uuid: string): Promise<boolean> {
      try {
        const response = await this.client.post(`/haproxy/settings/delFrontend/${uuid}`);
        if (response.result !== 'deleted') {
          throw new Error('Failed to delete frontend');
        }
        
        await this.reconfigure();
        return true;
      } catch (error) {
        throw new Error(`Failed to delete HAProxy frontend: ${error}`);
      }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this action is reversible, what permissions are required, what happens to associated resources, or what the response looks like. For a destructive operation with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple deletion operation and front-loads the essential information.

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

Completeness2/5

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

For a destructive deletion tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what happens after deletion, error conditions, or confirmation requirements. The combination of a mutation operation with minimal structured data requires more comprehensive description.

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 the single parameter 'uuid' documented as 'Frontend UUID'. The description adds no additional parameter information beyond what the schema already provides. With high schema coverage, the baseline score of 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?

The description clearly states the action ('Delete') and resource ('HAProxy frontend'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from sibling deletion tools like haproxy_backend_delete or delete_firewall_rule, which would require explicit differentiation to earn a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing the frontend UUID), when not to use it, or what alternatives exist (such as haproxy_frontend_list to verify before deletion).

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

Related 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/vespo92/OPNSenseMCP'

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