Skip to main content
Glama
gensecaihq

pfSense MCP Server

by gensecaihq

manage_bind_zone_record

Create or delete DNS records in BIND zones on pfSense by specifying hostname, record type, and data; apply changes immediately.

Instructions

Create or delete a DNS record within a BIND zone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRecord name/hostname (required for create, e.g., 'www', 'mail')
typeNoRecord type (required for create: A, AAAA, CNAME, MX, TXT, NS, PTR, SRV, etc.)
rdataNoRecord data (required for create, e.g., '192.168.1.10' for A record)
actionYesAction to perform ('create' or 'delete')
confirmNoMust be set to True for delete operations. Safety gate for destructive operations.
parent_idYesParent zone ID
record_idNoRecord 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 states the tool can delete records, which is destructive, but the annotations declare destructiveHint=false, creating a clear contradiction. The description also lacks additional behavioral context like the require confirm=true for delete or the effect of apply_immediately.

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 that efficiently conveys the tool's purpose. Every word earns its place, with no filler or repetition.

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

Completeness4/5

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

Given the rich schema and output schema, the minimal description is sufficient for an agent to select the tool, though it does not explicitly differentiate from zone-level management or highlight the dual-mode nature. The schema carries the load for parameter semantics and return values.

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?

The input schema has 100% description coverage, providing detailed meanings for all 8 parameters, including 'required for create' and 'required for delete' conditions. The tool description adds no extra parameter-level information, so the baseline 3 applies.

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 uses a specific verb+resource: 'Create or delete a DNS record within a BIND zone'. It clearly states the tool's function and differentiates from siblings like create_bind_zone (zone-level creation) and search_bind_zone_records (record listing).

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 provided on when to use this tool versus alternatives. There is no mention of exclusions or references to related tools such as search_bind_zone_records or manage_bind_access_list, leaving the agent to infer usage from the bare description.

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