Skip to main content
Glama
thinhost

thinhost-mcp

Official
by thinhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

provision_domain

Create a custom domain mapping for a deployed AI-generated site or app. Returns a claim URL for payment and DNS setup; the domain activates after completion.

Instructions

Provision a new custom domain for an AI-generated site or app.

Call this when a user wants their deployed site accessible at a custom domain. This creates the domain mapping and returns a claim_url where the user completes payment ($8/mo) and DNS setup. The domain is NOT immediately active — the user must visit the claim_url first.

Args: domain: The custom domain to provision (e.g., "mysite.com", "portfolio.dev") origin_url: The current URL where the site is hosted (e.g., "https://myapp.vercel.app") user_email: The end user's email address for billing and notifications idempotency_key: Optional key to prevent duplicate provisions on retry

Returns: provision_id: Unique ID to track this domain (use with check_domain_status) status: Current provisioning status enum (pending_payment, pending_dns, pending_ssl, active, failed, released) dns_instructions: Structured DNS record the user needs to create, plus a human_readable summary claim_url: URL to send the user to for payment and DNS setup walkthrough expected_completion_seconds: Estimated time for full provisioning after payment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
origin_urlYes
user_emailYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A5/5.0
Behavior5/5

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

No annotations provided, so the description carries the full burden, and it delivers a rich behavioral picture: it creates a mapping, is NOT immediately active, requires a post-step (claim_url visit), involves payment ($8/mo), and DNS setup. It also surfaces idempotency behavior. This is well beyond safe-read/write signaling.

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?

Front-loaded with purpose, then usage trigger, then Args and Returns. Every sentence earns its place: no restatement of schema titles, and the behavioral constraint is stated once, early, and clearly.

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 4-param, no-annotation, no-output-schema mutation tool, this definition is complete: arguments, return fields (including status enum values and dns_instructions shape), completion-time expectation, and the mandatory claim_url step. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate fully, and it does: domain (e.g., 'mysite.com'), origin_url (e.g., a deployed URL), user_email (billing/notifications purpose), and idempotency_key (retry-safety purpose) are all explained with examples and intent.

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 ('Provision a new custom domain for an AI-generated site or app') with the scope clearly bounded. Distinguishes itself from siblings like check_domain_status and release_domain by being the creation step in the lifecycle.

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?

Explicit trigger stated: 'Call this when a user wants their deployed site accessible at a custom domain.' The description also clarifies the workflow boundary (must visit claim_url first) and routes the agent to the sibling check_domain_status for tracking. Nothing left to inference.

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

Deploy Server

Other Tools