GleanMark USPTO Trademark Search

Check Domain Availability

check_domain_availability

Read-onlyIdempotent

Check domain availability for a brand name. Returns status (available, parked, commercially used, or taken) for each TLD, plus .com variations (e.g., getbrand.com, brandhq.com).

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": {
      "brand_name": "<brand_name>"
    },
    "name": "check_domain_availability"
  }
}

Input Schema

Name	Required	Description	Default
`tlds`	No	TLDs to check. Defaults to com/ai/app/io/co when omitted.
`brand_name`	Yes	Brand name to check (e.g., "Moonlight Coffee")

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 11, 2026

changedInput schema / properties / tlds / default

Previous value: -[
-  "com",
-  "ai",
-  "io"
-]New value: +[
+  "com",
+  "ai",
+  "app",
+  "io",
+  "co"
+]

changedInput schema / properties / tlds / description

Previous value: -"TLDs to check"New value: +"TLDs to check. Defaults to com/ai/app/io/co when omitted."

AddedMar 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the operation read-only, open-world, and idempotent; the description adds meaningful behavioral detail by enumerating the possible statuses and the inclusion of .com variations. This goes beyond the annotation-only baseline without contradicting it.

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?

The description is a compact two-sentence definition with no filler. The core purpose is front-loaded and the added return detail is essential and concise.

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?

For a simple read-only lookup tool with fully documented parameters and no output schema, the description covers both input scope and output shape. Nothing critical is missing for an agent to invoke it correctly.

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%, with both brand_name and tlds already documented. The description adds no extra parameter-level semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the verb ('Check') and the resource ('domain availability for a brand name'), and it enumerates the output statuses and .com variations. It is specific enough to distinguish from sibling tools like check_brand_availability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: whenever an agent needs to check domain availability for a brand. However, it provides no explicit guidance on when not to use it or how it relates to sibling tools such as check_brand_availability.

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

All GleanMark USPTO Trademark Search 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.

Resources

Need Help?