Skip to main content
Glama

pve_sdn_dns_update

Update an existing SDN DNS integration in Proxmox. Dry-run by default to review changes before applying with confirmation.

Instructions

MUTATION: update an SDN dns integration (PENDING). type is IMMUTABLE. reversev6mask does NOT exist on this endpoint — only reversemaskv6 (schema asymmetry vs. create, see pve_sdn_dns_create's own docstring).

key (if given) is redacted in the returned PLAN and never written to the audit ledger. To create a new integration use pve_sdn_dns_create; to remove one use pve_sdn_dns_delete. Dry-run by default (returns a PLAN, with the current config CAPTURED and redacted); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dnsYesExisting SDN dns integration id to update.
keyNoNew PowerDNS API key — a SECRET, masked in plans/the ledger; forwarded raw on the wire.
urlNoNew PowerDNS API base URL.
deleteNoField names to unset.
digestNoExpected config digest for optimistic-concurrency checking.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
dns_ttlNoDNS record TTL in seconds (wire key 'ttl' — see pve_sdn_dns_create's own note on the param-name split).
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.
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
Behavior4/5

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

Discloses mutation nature, immutability of type, redaction of key, schema asymmetry, and dry-run staging. No annotations provided, so description carries full burden; slight misses on error details.

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 5-sentence description, front-loaded with 'MUTATION', no unnecessary words.

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 overall workflow, immutability, redaction, sibling differentiation, and staging. Missing some error handling context, but output schema exists to complement.

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 covers 100% parameters with descriptions. Description adds value on reversemaskv6 asymmetry and key redaction, but mostly redundant with schema. Baseline 3 is appropriate.

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?

Description clearly states it updates an SDN DNS integration. References siblings for create and delete, distinguishing its purpose.

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 directs to use pve_sdn_dns_create for creation and pve_sdn_dns_delete for removal. Also explains dry-run vs confirm behavior.

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