Skip to main content
Glama
gensecaihq

pfSense MCP Server

by gensecaihq

manage_haproxy_file

Create or delete HAProxy files such as certificates, error pages, or Lua scripts. Use content to create, confirm to delete, and apply changes immediately.

Instructions

Create or delete an HAProxy file (certificate, error page, Lua script, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFile name (required for create)
actionYesAction to perform ('create' or 'delete')
confirmNoMust be set to True for delete operations. Safety gate for destructive operations.
contentNoFile content (used for create)
file_idNoFile ID (required for delete)
apply_immediatelyNoWhether to apply changes immediately

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

The description contradicts the annotations: destructiveHint is false, but the tool explicitly supports deleting files, and the schema confirms that delete is destructive with a confirm safety gate. This is a serious inconsistency that misleads the agent about the tool's safety profile.

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, front-loaded sentence with zero wasted words, effectively conveying the tool's purpose.

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?

Despite the output schema and full parameter documentation, the description is incomplete due to the destructiveHint contradiction and lacks context on related actions like apply_haproxy_changes. The agent is left uncertain about safety and next steps.

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%, so the schema already documents all six parameters. The description adds minimal semantic context by giving examples of file types, but it does not explain parameters beyond what the schema provides.

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 clearly states the action (create or delete), the resource (HAProxy file), and provides examples of file types, making it distinct from siblings like search_haproxy_files and create_haproxy_frontend.

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?

No guidance is given on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description simply states the action without context on selection.

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/gensecaihq/pfsense-mcp-server'

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