SORNKan Publish

edit

Check the zip for unsafe files, then redeploy the live Worker. Flat $0.50 per edit on every rail (x402 wallet or card/PromptPay payment_url). Does not extend lease days. Ownership: a site claimed with a wallet must be edited by paying from that same wallet; a site paid by card/PromptPay needs its editToken (shown once at claim and emailed to the payer). 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

Name	Required	Description
`slug`	Yes	Live site slug to redeploy
`tokens`	No	Approximate token size of the change (optional, informational — edits are flat $0.50)
`uploadId`	Yes	UUID of the new zip to deploy (call upload_url first)
`editToken`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / slug / description
```
Added value: +"Live site slug to redeploy"
```

addedInput schema / properties / tokens / description

Added value: +"Approximate token size of the change (optional, informational — edits are flat $0.50)"

addedInput schema / properties / uploadId / description

Added value: +"UUID of the new zip to deploy (call upload_url first)"

Changed2 schema fields changedOct 15, 2026

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"
+}

removedInput schema / properties / ownerWallet
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedAug 26, 2026
- addedInput schema / properties / ownerWallet
```
Added value: +{
+  "type": "string"
+}
```

Changed7 schema fields changedAug 21, 2026

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 / tokens / description

Removed value: -"Optional billed token count for JS review. Omit for static HTML. Floor charge is still $0.10 USDC."

removedInput schema / properties / tokens / minimum
```
Removed value: -0
```

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)$"

Changed7 schema fields changedAug 21, 2026

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 / tokens / description

Added value: +"Optional billed token count for JS review. Omit for static HTML. Floor charge is still $0.10 USDC."

addedInput schema / properties / tokens / minimum
```
Added value: +0
```

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)$"

First observedAug 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only cover the safety profile (non-read-only, non-idempotent, open-world, not destructive), so the description carries real weight: it discloses flat $0.50 pricing across both rails, wallet-to-site ownership binding, the one-time editToken requirement, and that the edit does not extend the lease. It stops short of describing the failure modes beyond the 402 flow.

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 action, then pricing, then ownership rules, then the no-wallet fallback — a sensible order. It is dense and packed into a single paragraph with several parentheticals, which slightly hurts scannability.

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 to expect back (a 402 with payment_url) and how to confirm completion (poll preview_status/retry until live). Payment, ownership, and completion signals are all covered, so nothing needed 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 per-parameter descriptions already define slug, uploadId, editToken, and tokens. The description adds genuine conditional meaning on top, clarifying when editToken is required (card/PromptPay sites) and confirming tokens is informational only.

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: scan the uploaded zip, then redeploy the live Worker for a slug. It also implicitly separates itself from siblings by noting it 'does not extend lease days' (vs. renew) and by pointing at upload_url/preview_status as adjacent steps.

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 explicit selection conditions: wallet-claimed sites must pay from the same wallet, card/PromptPay sites need an editToken, and agents with no wallet should surface the 402 payment_url to a human and then poll preview_status/retry. Both the happy path and the fallback path are spelled out.

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

All SORNKan Publish tools Inspect

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

Need Help?