Skip to main content
Glama

Brand, Domain & USPTO Trademark Availability Check

check_brand_availability
Read-onlyIdempotent

Screen a candidate brand or product name across .com, .io, .ai, .dev, developer handles, and USPTO trademarks; get a 0–100 Brand Readiness Score before registering.

Instructions

Check a single candidate startup or product name across top TLDs (.com, .io, .ai, .dev via live RDAP/DNS), public developer handles (GitHub, npm, PyPI, Bluesky), and live USPTO trademark records, returning a 0-100 Brand Readiness Score. Use this tool when evaluating candidate names before registering a domain; use full_launch_readiness_audit instead when auditing an already-chosen domain across brand, email DNS, and AI search visibility together.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCandidate brand or product name to screen (alphanumeric label, e.g. 'linear' or 'resend').
tldsNoOptional list of domain extensions without leading dots (defaults to ['com', 'io', 'ai', 'dev'], max 6).

Output Schema

NameRequiredDescriptionDefault
gradeYesLetter grade from A to D.
scoreYes0-100 Brand Readiness Score.
issuesYesDetected naming or conflict blockers.
domainsYesPer-TLD RDAP/DNS registration statuses.
handlesNoPublic handle availability statuses.
candidateYesNormalized lowercase brand label.
checkedAtYesISO-8601 UTC timestamp of the live check.
trademarksNoMatched live USPTO trademark filings, if any.
upgradeLinksNoLinks for batch CSV screening and Nice Class clearance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered; the description adds useful non-annotation context by naming the live data sources (live RDAP/DNS, live USPTO records), which implies external calls and non-deterministic freshness. It stops short of disclosing latency, rate limits, or what happens when a TLD lookup fails, keeping it below a 5.

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?

Two sentences, front-loaded with the operation and data sources, followed by the routing guidance. The parenthetical source lists are dense but each item is informative; there is no filler or repetition.

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?

Given an output schema exists, the description needn't explain the return payload, yet it still surfaces the headline 0-100 score. The main remaining gap for an open-world, network-dependent tool is expected runtime or partial-failure behavior, which is not addressed.

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%, so both parameters are already documented, including the default TLD list and the max-6 cap. The description reinforces the default TLD set ('.com, .io, .ai, .dev') but adds no new semantics such as accepted name formats or what happens when a name is invalid, so baseline 3 applies.

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?

Uses a specific verb ('Check') plus a precisely scoped resource: a single candidate name against named TLDs, developer handles (GitHub, npm, PyPI, Bluesky) and live USPTO records, plus an explicit '0-100 Brand Readiness Score' output. This distinguishes it clearly from the sibling audit tools without the reader opening any schema.

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?

States the exact use case ('evaluating candidate names before registering a domain') and names the alternative sibling `full_launch_readiness_audit` together with the condition that selects it (auditing an already-chosen domain across brand, email DNS and AI visibility together). Both the when and the when-not are explicit.

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