Skip to main content
Glama
lucamarien

OPNsense MCP Server

by lucamarien

opn_add_ddns_account

Create a Dynamic DNS account to automatically update a hostname's DNS record when the firewall's public IP changes. Registers with providers like Cloudflare, No-IP, or DynDNS.

Instructions

Create a new Dynamic DNS account and apply the configuration.

Use this to register a hostname with a DDNS provider so the firewall automatically updates the DNS record when the public IP changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesDDNS provider name (e.g. 'cloudflare', 'dyndns', 'noip', 'freedns', 'he', 'namecheap', 'desec', 'godaddy').
hostnameYesFully qualified domain name to update (e.g. 'fw.example.com').
usernameNoProvider username or API key (leave empty for token-only providers).
passwordNoProvider password or API token.
checkipNoIP check method — 'web_dyndns' (default), 'web_freedns', 'web_he', 'if' (use interface IP), or 'cmd'. For IPv6: use 'web_dyndns6', 'web_freedns6', etc. The global 'allowipv6' setting must ALSO be enabled or IPv6 updates silently fail.web_dyndns
interfaceNoNetwork interface name (e.g. 'wan', 'opt1'). Required when checkip='if'. Optional otherwise.
descriptionNoOptional description for this account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It implies a write operation but does not mention authentication requirements, side effects (e.g., immediate application, need for commit), or potential failure modes. This is a significant gap.

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 two sentences, the first stating the action and the second providing context. It is concise, front-loaded, and contains no filler.

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

Completeness3/5

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

Given the presence of an output schema and high schema coverage, the description is mostly complete for parameter understanding. However, it lacks behavioral transparency and usage exclusions, leaving some gaps for an agent.

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 detailed parameter descriptions (e.g., checkip explains IPv6). The description adds no extra semantics beyond the schema, meeting baseline of 3.

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 tool creates a new Dynamic DNS account and applies configuration. It distinguishes from sibling tools like opn_list_ddns_accounts, opn_update_ddns_account, opn_delete_ddns_account by focusing on creation.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to register a hostname with a DDNS provider for automatic IP updates). It does not explicitly state when not to use it or compare alternatives, but the context is clear enough for most agents.

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/lucamarien/opnsense-mcp-server'

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