Popdot AI

check_availability

Read-only

Check whether a specific subdomain is available on a given domain for a paid rental. Returns true if the subdomain can be rented. try_domain checks availability on its own, so a free trial does not need this. Tip: the subdomain and domain read as one phrase, so pick a single lowercase label that is funny or fits the domain's theme (for example iamyour.slopmommy.com or analien.lostmyluggage.com). A delightful combination is the point of a Popdot AI address.

Input Schema

Name	Required	Description	Default
`domainId`	Yes	The parent domain: its id from search_domains, or its name (for example addedtocart.shop)
`subdomain`	Yes	The subdomain label to check (e.g., 'myproject' for myproject.example.com)

Output Schema

Name	Required	Description	Default
`reason`	No
`fullUrl`	No
`domainId`	Yes
`available`	Yes
`subdomain`	Yes
`fullDomain`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / domainId / description

Previous value: -"The unique ID of the parent domain"New value: +"The parent domain: its id from search_domains, or its name (for example addedtocart.shop)"

Changed1 schema field changedAug 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "domainId": {
+      "type": "string"
+    },
+    "fullDomain": {
+      "type": "string"
+    },
+    "fullUrl": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "subdomain": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "domainId",
+    "subdomain",
+    "available"
+  ],
+  "type": "object"
+}

First observedJul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the boolean return contract and the non-obvious behavior that domain and subdomain are read as one combined phrase. It does not mention auth or rate limits, but for a read-only check that is a minor omission.

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

Conciseness4/5

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

Purpose and return value are front-loaded, then the alternative tool, then the naming tip. Most sentences earn their place; the closing line about 'a delightful combination' is light marketing padding, but it reinforces the naming constraint rather than derailing.

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?

An output schema exists, so return values need no explanation, and the description still states the boolean outcome. It covers the subdomain-naming edge case that the schema alone leaves ambiguous; only missing downstream guidance (this is a check, not the rental itself) keeps it from a 5.

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, and the description adds genuine semantics beyond the schema: the label must be a single lowercase token that combines with the domain into one readable phrase, with concrete examples.

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 and resource (check subdomain availability on a domain) and explicitly scopes it to paid rentals. It also differentiates from the sibling try_domain, so an agent can pick between them without opening a schema.

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?

Gives an explicit when-not rule: try_domain already checks availability, so a free trial does not need this call. It stops short of naming rent_domain / get_price_quote as the downstream steps, but the paid-vs-trial condition is clear.

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

All Popdot AI tools Inspect

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.