Skip to main content
Glama

SORNKan Publish

by com.sornkan
OverviewDiscussionsAdmin

connect_custom_hostname

Connect an existing hostname via CNAME to sites.sornkan.com (no registrar). One-time $1 USDC, same claiming wallet (or editToken for a card-paid site), while lease is live. If the bind is refused after a card payment, the payment stays as a credit: retry with HTTP POST https://publish.sornkan.com/custom-hostname {slug, hostname} plus header X-Edit-Token — no new payment. If the hostname is already on Cloudflare, keep the CNAME proxied. Not a monthly fee. If you have no wallet, get payment_url from the 402 response and show it to the human — they pay by card or Thai PromptPay in THB (no crypto needed); after they pay, poll preview_status/retry until live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesLive site slug to attach the hostname to
hostnameYesYour own domain to point at the site (e.g. www.example.com); CNAME it to sites.sornkan.com
editTokenNoEdit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / hostname / description
      Added value: +"Your own domain to point at the site (e.g. www.example.com); CNAME it to sites.sornkan.com"
    • addedInput schema / properties / slug / description
      Added value: +"Live site slug to attach the hostname to"
  2. Changed1 schema field changed
    • addedInput schema / properties / editToken
      Added value: +{
+  "description": "Edit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site.",
+  "type": "string"
+}
  3. Changed4 schema fields changed
    • removedInput schema / properties / hostname / description
      Removed value: -"A hostname the human already owns (example: shop.example.com). This tool does not register domains."
    • removedInput schema / properties / hostname / minLength
      Removed value: -1
    • removedInput schema / properties / slug / description
      Removed value: -"Live site slug: lowercase letters, digits, and hyphens, max 40 chars. Becomes worldsite-site-{slug}.workers.dev."
    • removedInput schema / properties / slug / pattern
      Removed value: -"^[a-z0-9-]{1,40}$"
  4. Changed4 schema fields changed
    • addedInput schema / properties / hostname / description
      Added value: +"A hostname the human already owns (example: shop.example.com). This tool does not register domains."
    • addedInput schema / properties / hostname / minLength
      Added value: +1
    • addedInput schema / properties / slug / description
      Added value: +"Live site slug: lowercase letters, digits, and hyphens, max 40 chars. Becomes worldsite-site-{slug}.workers.dev."
    • addedInput schema / properties / slug / pattern
      Added value: +"^[a-z0-9-]{1,40}$"
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the generic safety profile (write, open-world, not idempotent, non-destructive). The description adds substantial behavior: a one-time $1 USDC charge, credit retention if the bind is refused after card payment, the raw HTTP POST retry path with X-Edit-Token, Cloudflare proxying advice, and post-payment polling. None of this is inferable from structured fields.

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?

Front-loads the core action and then layers payment, retry, and fallback details efficiently in a few dense sentences. The inline HTTP POST fallback is arguably operational detail rather than tool-invocation guidance, but almost every clause carries needed context.

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?

With no output schema, the description still tells the agent what happens after invocation: poll preview_status/retry until the hostname is live, and how to recover from a refused bind. Payment paths (crypto wallet vs. card/PromptPay) and the credit fallback are all covered, so an agent can complete the workflow.

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 slug, hostname, and editToken are already documented in the schema. The description reinforces when editToken matters (card-paid sites) and the CNAME target, but adds little semantic detail beyond the schema.

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: connect an existing hostname via CNAME to sites.sornkan.com. It explicitly scopes itself ('no registrar') and is clearly distinguishable from siblings like claim, renew, and edit.

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 clear when-to-use context: requires a live lease, the same claiming wallet or an editToken for card-paid sites, and routes wallet-less users to the 402 payment_url plus preview_status polling. It names a sibling (preview_status) but never states explicit exclusions versus other hostname-related operations.

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

All SORNKan Publish toolsInspect
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