Skip to main content
Glama
Sign In

Squish

by co.squish
OverviewDiscussionsAdmin

Create dns record

create_dns_record

Create a new DNS record on a domain the customer owns. Two-step usage: (1) call with confirm:false to preview the new record and describe it to the user, then (2) ONLY after the user explicitly says yes, call again with confirm:true. NEVER call confirm:true without explicit user confirmation.

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>",
      "type": "<type>",
      "value": "<value>"
    },
    "name": "create_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNoOptional TTL in seconds (default 3600, range 60-86400).
hostNoSubdomain host (relative, e.g. "www" or "@" / "" for apex).
typeYesRecord type: A, AAAA, CNAME, MX, TXT, NS, or SRV.
valueYesValue (IP, hostname, text, etc.).
domainYesDomain to add the record to.
confirmNofalse (default) returns preview; true creates it. Pass true ONLY after explicit user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

The annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false but say nothing about the consent gate, so the description does real work by disclosing the mandatory preview-then-confirm behavior. It does not cover other behavioral details such as what the preview contains, what happens on duplicate or conflicting records, or whether a failed create is reported or retried.

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 short sentences, the consent gate is front-loaded and reinforced rather than padded, and no clause merely restates the name or title.

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 mutating tool with no output schema and fully documented params, it covers ownership, the workflow, and the safety gate, which is the bulk of what an agent requires. It stops short of stating what the preview reveals or how create-time errors surface, a modest gap given the tool's risk profile.

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?

With 100% schema description coverage, every parameter is already documented, including the meaning of confirm and its default. The description reinforces the confirm sequencing but adds no new semantics for domain, type, host, value, or ttl, so the baseline of 3 applies.

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?

"Create a new DNS record on a domain the customer owns" gives a specific verb and resource plus an ownership scope. It implicitly separates the tool from update_dns_record and delete_dns_record through the word "new," but never names those siblings, so the agent has to infer the create-vs-update boundary.

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?

It gives an explicit two-step protocol: first confirm:false to preview and describe to the user, then confirm:true only after explicit user confirmation, with a hard NEVER on skipping consent. That is exactly the when-to-use and when-not-to-use guidance an agent needs for a risky write.

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