Skip to main content
Glama
Sign In

SORNKan Publish

by com.sornkan
OverviewDiscussionsAdmin

claim

Claim (activate) an inspected preview as a live site at {slug}.worldsite.workers.dev. This is the paid go-live step ($1 USDC first 30 days); publish_website only returns the plan and never goes live by itself. Call preview_status first — if claimable is false, do not pay. Ask which slug they want before paying. Live URL is {slug}.worldsite.workers.dev — not {slug}.workers.dev. Pretty names: CNAME their domain after claim. uploadId MUST be the UUID from inspect (not previewUrl). If you only have https://publish.sornkan.com/preview/, pass that UUID. 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. If the last claim returned PRICE_COMPUTE_FAILED, retry this tool — no USDC was taken. If a signed payment failed settlement, tell the human contact@sornkan.com and do not retry payment.

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

Input Schema

NameRequiredDescriptionDefault
slugNoLowercase site name to claim; live URL is {slug}.worldsite.workers.dev (ask the human first)
emailNoReceipt email for card/PromptPay payers (optional)
uploadIdYesUUID from inspect — the part after /preview/, never the full preview URL
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. Changed3 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"Receipt email for card/PromptPay payers (optional)"
    • addedInput schema / properties / slug / description
      Added value: +"Lowercase site name to claim; live URL is {slug}.worldsite.workers.dev (ask the human first)"
    • addedInput schema / properties / uploadId / description
      Added value: +"UUID from inspect — the part after /preview/, never the full preview URL"
  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. Changed1 schema field changed
    • addedInput schema / properties / email
      Added value: +{
+  "type": "string"
+}
  4. Changed5 schema fields changed
    • 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}$"
    • removedInput schema / properties / uploadId / description
      Removed value: -"UUID returned by upload_url that identifies the stored zip. Example: 00000000-0000-4000-8000-000000000001."
    • removedInput schema / properties / uploadId / format
      Removed value: -"uuid"
    • removedInput schema / properties / uploadId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  5. Changed5 schema fields changed
    • 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}$"
    • addedInput schema / properties / uploadId / description
      Added value: +"UUID returned by upload_url that identifies the stored zip. Example: 00000000-0000-4000-8000-000000000001."
    • addedInput schema / properties / uploadId / format
      Added value: +"uuid"
    • addedInput schema / properties / uploadId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the generic read/write/idempotency profile; the description goes well beyond them by disclosing the $1 USDC cost, the 402/payment_url card-PromptPay fallback in THB, the PRICE_COMPUTE_FAILED retry rule with 'no USDC taken', and the do-not-retry escalation path for failed settlements. These are exactly the non-obvious behavioral facts an agent needs before triggering a paid, non-idempotent operation.

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-loaded with the core action and price, then ordered by decision point (precheck → human → payment → failure branches). It is dense and long, and a few clauses (pretty-name CNAME) sit mid-stream, but essentially every sentence carries operational information rather than filler.

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 paid, mutating tool with no output schema and only one required parameter, the description covers the full lifecycle: preconditions, cost, success URL shape, payment alternatives for wallet-less agents, polling after payment, and the two distinct failure recoveries. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: it clarifies uploadId must be the UUID 'not previewUrl' and shows how to extract it from a full preview URL, and it warns the live URL is {slug}.worldsite.workers.dev rather than {slug}.workers.dev. Some of this overlaps the schema text, which keeps it from a 5.

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 (claim/activate) plus resource (inspected preview → live site), and immediately pins the resulting artifact: {slug}.worldsite.workers.dev. It also explicitly differentiates from the sibling publish_website, which 'only returns the plan and never goes live by itself.'

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?

Gives an explicit prerequisite chain (inspect → preview_status → claim), an exclusion rule ('if claimable is false, do not pay'), a human-confirmation step ('ask which slug they want before paying'), and names the fallback siblings to poll (preview_status/retry). Nothing about when to invoke this vs. neighbors is left to inference.

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