Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Delete a DNS record

eurodns_dns_delete_record
DestructiveIdempotent

Delete a DNS record from a zone by record ID or by type and host. Provide exact rdata when several records share type and host to avoid ambiguous selection; read the zone first.

Instructions

Deletes one DNS record from a zone, either by its numeric recordId or by type and host, resolving the id from the live zone in the second case. Give rdata as well when several records share a type and host: an ambiguous selection is refused rather than guessed. Read the zone first with eurodns_dns_get_zone to see what it holds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoNode the record applies to. Use "" or "@" for the apex. Required without recordId.
typeNoRecord type of the record to delete, e.g. A, CNAME, TXT. Required without recordId.
rdataNoExact current value, to disambiguate.
recordIdNoNumeric id of the record, from the records eurodns_dns_get_zone returns. When given, type and host are not needed.
domainNameYesZone to modify, e.g. example.com.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.10.0
    • changedInput schema / properties / host / description
      Previous value: -"Node the record applies to. Use \"\" or \"@\" for the apex."New value: +"Node the record applies to. Use \"\" or \"@\" for the apex. Required without recordId."
    • addedInput schema / properties / recordId
      Added value: +{
+  "description": "Numeric id of the record, from the records eurodns_dns_get_zone returns. When given, type and host are not needed.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Record type of the record to delete."New value: +"Record type of the record to delete, e.g. A, CNAME, TXT. Required without recordId."
    • changedInput schema / required
      Previous value: -[
-  "domainName",
-  "type",
-  "host"
-]New value: +[
+  "domainName"
+]
    • changedOutput schema / properties / deleted / required
      Previous value: -[
-  "id",
-  "type",
-  "host",
-  "rdata"
-]New value: +[
+  "id"
+]
  2. First observedv0.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable behavioral detail beyond these: it resolves the record id from the live zone when type/host are given, and it refuses ambiguous selections rather than guessing. This gives an agent realistic expectations about failure modes and safety without contradicting the annotations.

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?

Three sentences, each earning its place: the main action and modes, the ambiguity safety rule, and the prerequisite read step. The most important information is front-loaded and there is no redundant phrasing or repetition of schema details.

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

Completeness5/5

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

Given the tool's moderate complexity and the presence of an output schema, the description covers everything an agent needs to select and invoke it correctly: the two identification strategies, disambiguation rule, and a concrete precondition. Return values are already documented by the output schema, so no gap remains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description enhances the schema by explaining the relationship between recordId and type/host (mutually exclusive paths) and clarifying when rdata is necessary ('several records share a type and host'). This adds meaning beyond the individual property descriptions.

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 states a specific action ('Deletes one DNS record from a zone') and names the two distinct invocation modes (by recordId or by type and host). This clearly distinguishes it from sibling tools like eurodns_dns_add_records and eurodns_dns_upsert_record, making its purpose unambiguous.

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 gives clear context on how to identify the target record and explicitly advises reading the zone first with eurodns_dns_get_zone. It does not explicitly enumerate when not to use this tool versus alternatives like save_zone, but the selection logic and prerequisite are valuable enough to earn a 4.

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/JigSawFr/eurodns-mcp'

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