Skip to main content
Glama
Sign In

Squish

by co.squish
OverviewDiscussionsAdmin

Delete dns record

delete_dns_record
Destructive

Delete a DNS record on a domain the customer owns. Two-step usage REQUIRED: (1) call with confirm:false to fetch the record being deleted and describe EXACTLY what will be removed (record type, host, value) — deletion is irreversible and the user must understand what they're losing. (2) ONLY after the user explicitly says yes, call again with confirm:true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "recordId": "<recordId>"
    },
    "name": "delete_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain the record lives on.
confirmNofalse (default) returns preview; true deletes the record. Pass true ONLY after explicit user confirmation.
recordIdYesNameSilo record ID to delete — get it from get_dns_records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them by disclosing that deletion is irreversible and that a preview step exists to enumerate exactly what is lost. It does not cover failure modes (e.g., record no longer exists, domain lock) or anything about rate limits, so it falls just short of full behavioral disclosure.

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?

Two sentences, front-loaded with the irreversible-destruction warning before the procedure. Numbered steps make the sequence scannable and every clause carries operational weight.

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?

For a destructive 3-parameter tool with no output schema, the definition covers safety, sequencing, and preview content well. It omits what happens on a failed/unknown recordId and whether the preview persists, but nothing essential to correct invocation is missing.

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 baseline is 3, but the description adds protocol-level meaning to 'confirm' (the false→true sequencing tied to user consent) and implies recordId is sourced from get_dns_records via the schema. The added semantics for confirm go slightly beyond the schema's one-line description.

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?

States a specific verb+resource ('Delete a DNS record') scoped to 'a domain the customer owns', which cleanly separates it from create_dns_record and update_dns_record among the siblings. The third sentence even specifies what the preview must report (record type, host, value), so the agent knows the shape of the operation.

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?

Gives an explicit, mandatory two-step protocol: first call with confirm:false, then only after explicit user yes with confirm:true. This is unambiguous when-to-use guidance including the gating condition, not mere implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Squish toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources