Skip to main content
Glama

pve_sdn_dns_create

Create a pending SDN DNS integration for PowerDNS. Requires API URL and key; returns a plan by default, confirm to execute.

Instructions

MUTATION: create an SDN dns integration (PENDING — inert until pve_sdn_apply).

url/key are REQUIRED. key is a SECRET — redacted to "[redacted]" in the returned PLAN and never written to the audit ledger; the real create call still carries it raw (the mutation must actually work). To update an existing integration use pve_sdn_dns_update; to remove one use pve_sdn_dns_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending integration, returning {status, result}. RISK_LOW (staging, no live network effect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dnsYesNew SDN dns integration id to create.
keyYesPowerDNS API key — a SECRET, masked in plans/the ledger; forwarded raw on the wire so the create actually works.
urlYesPowerDNS API base URL.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
dns_ttlNoDNS record TTL in seconds (wire key 'ttl' — named dns_ttl here because this codebase reserves the bare 'ttl' parameter name for the out-of-band arm-lease mechanism).
dns_typeNoDns plugin type — only 'powerdns' exists today.powerdns
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
fingerprintNoCertificate SHA-256 fingerprint (colon-separated hex byte pairs).
reversemaskv6NoIPv6 reverse-zone mask length.
reversev6maskNoIPv6 reverse-zone mask length (create-only field — not accepted on update; schema asymmetry, see module docstring).
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden; it discloses mutation, pending status, dry-run, secret handling (redacted in plan/ledger), and risk level.

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?

Concise yet comprehensive; front-loads mutation and pending nature, uses structured format with bullet points and capitalizes key terms.

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?

Covers behavior, required params, security, dry-run, and risk level; output schema exists so return values not needed. Could optionally explain lock_token and proximo_target but schema handles them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value by explaining key secret behavior, confirm parameter, dns_ttl naming quirk, and default for dns_type.

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?

Clearly states it's a mutation to create an SDN DNS integration and notes it is pending until pve_sdn_apply, distinguishing it from update, delete, and get siblings.

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?

Explicitly states required parameters (url, key), dry-run default vs confirm=True, and references siblings pve_sdn_dns_update/pve_sdn_dns_delete for alternatives.

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/john-broadway/proximo'

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