Skip to main content
Glama

pve_sdn_dns_delete

Delete an SDN DNS integration; dry-run returns plan, confirm=true executes removal.

Instructions

MUTATION: delete an SDN dns integration (PENDING). Dry-run by default — the PLAN shows the current integration (with key redacted if present).

Referential-integrity refusal is asserted BY ANALOGY only — Smoke-confirm. confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the integration (re-supplying the key) to revert. RISK_MEDIUM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dnsYesExisting SDN dns integration id to delete.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
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 key behavioral traits: dry-run by default, PLAN output with redacted key, confirm executes removal returning {status, result}, no config undo, risk medium. With no annotations, this provides substantial transparency beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose but contains jargon ('MUTATION:', 'BY ANALOGY only — Smoke-confirm') that reduces clarity. Slightly verbose but not excessively long.

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 dry-run behavior, confirm action, irreversibility, and risk. With output schema present, the description adequately complements structured fields, though some phrasing (referential-integrity analogy) is opaque.

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 coverage is 100%, so the description adds minimal value for parameters. It mentions 'key' in the plan output but not as a parameter. Does not extend beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool deletes an SDN DNS integration, distinguishing it from sibling create/get/list/update tools. The '(PENDING)' adds minor ambiguity, but the verb 'delete' and resource 'SDN dns integration' are explicit.

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 explicit guidance on when to use this tool versus alternatives like pve_sdn_dns_update. The description mentions dry-run vs confirm but does not differentiate from other SDN DNS tools or provide context for 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/john-broadway/proximo'

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