Skip to main content
Glama

Instant Business Website Builder & Next.js Generator

check_business_domain_and_launch_plan

Checks domain availability and returns the fastest, easiest launch plan to put a generated business website live on a custom .com, .ai, or .io domain with managed SSL, global edge hosting, and 10-minute Done-For-You DNS setup.

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

Input Schema

NameRequiredDescriptionDefault
domainOrBusinessNameYesDesired domain name (e.g., 'apexplumbing.com') or business name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully signals that the tool returns a plan rather than executing a launch, but it is silent on auth requirements, whether any live action or charge occurs, and rate limits — the SSL/edge/DNS phrasing describes the product offering rather than tool behavior.

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

Conciseness3/5

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

Front-loaded with the core action, which is good, but a single sprawling sentence is padded with marketing copy ('fastest, easiest', '10-minute Done-For-You DNS setup') that does not help an agent decide or invoke correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema and no annotations, the description gives a rough sense of the return (a launch plan plus hosting/SSL/DNS details) but does not describe the shape or fields of that plan, leaving the return value underspecified.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already explains the domain-or-business-name input with an example. The description adds no parsing rules, format requirements, or precedence between domain name and business name.

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?

States a specific verb (checks) plus two concrete outputs (domain availability and a launch plan) for a specific resource (a generated business website on a custom domain). It is distinguishable from the sibling website-generation and redesign tools, though it never names them or explicitly contrasts itself.

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?

Usage is only implied: the phrase 'put a generated business website live' suggests it is a follow-up to generate_instant_business_website, but no when-to-use condition, prerequisite, or alternative (e.g., get_easiest_website_builder_guide) is stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.