ShipStatic

Check Domain Availability

domains_validate

Read-only

Check if a domain name is valid and available before creating it. Returns the normalized form and availability.

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>"
    },
    "name": "domains_validate"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to check (e.g. "yourname.shipstatic.com" or "www.example.com"). Call before domains_set to check availability.

Output Schema

Name	Required	Description
`valid`	Yes	Whether the domain's shape is usable.
`reason`	Yes	Why the name is unusable, for display; null when it is usable.
`available`	Yes	Whether nobody has registered the name yet; null when invalid. Creating it would be new; re-pointing your own domain is a write, not a create.
`normalized`	Yes	The normalized domain name; null when invalid.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain name to check (e.g. \"www.example.com\"). Call before domains_set to check availability."New value: +"Domain name to check (e.g. \"yourname.shipstatic.com\" or \"www.example.com\"). Call before domains_set to check availability."

Changed6 schema fields changedSep 23, 2026

removedOutput schema / properties / available / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / available / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / normalized / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / normalized / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / reason / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedSep 17, 2026

changedOutput schema / properties / available / description

Previous value: -"Whether the domain is available; null when invalid."New value: +"Whether nobody has registered the name yet; null when invalid. Creating it would be new; re-pointing your own domain is a write, not a create."

changedOutput schema / properties / reason / description

Previous value: -"Why the name is unusable, for display; null when valid."New value: +"Why the name is unusable, for display; null when it is usable."

changedOutput schema / properties / valid / description

Previous value: -"Whether the domain name is valid."New value: +"Whether the domain's shape is usable."

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "available": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether the domain is available; null when invalid."
+    },
+    "normalized": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The normalized domain name; null when invalid."
+    },
+    "reason": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Why the name is unusable, for display; null when valid."
+    },
+    "valid": {
+      "description": "Whether the domain name is valid.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "valid",
+    "normalized",
+    "available",
+    "reason"
+  ],
+  "type": "object"
+}

AddedAug 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the call performs both validity and availability checking and returns a normalized form, which tells the agent this is a pre-flight gate rather than a plain lookup.

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 tight sentences, with the purpose and the pre-creation timing front-loaded and no filler. Every clause earns its place.

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?

With an output schema present and annotations covering the safety profile, the description only needs to convey what the tool does and when to use it, which it does. It could go slightly further by noting that a passing check does not reserve the domain, but nothing essential for correct invocation is missing.

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 description coverage is 100% for the single domain parameter, including an example format and a pointer to domains_set, so the schema carries the parameter semantics. The description adds no format or syntax detail beyond what the schema already states, which is the baseline 3 case.

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 gives a specific verb+resource ("check if a domain name is valid and available") and states the scope precisely. It implies the sibling relationship with domains_set via "before creating it," though it does not name that sibling explicitly, so it stops short of a 5.

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?

"Check ... before creating it" gives clear timing guidance for when to reach for this tool rather than domains_set. There are no explicit exclusions or alternative-branch conditions, but the usage context is unambiguous.

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

All ShipStatic tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.