Skip to main content
Glama

SORNKan Worldsite

by com.sornkan
OverviewDiscussionsAdmin

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) unless a complimentary edit remains. Same claiming wallet. Does not extend lease days. 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. Wallet-less owners: pass ownerWallet (the address that claimed this slug) so the 402 carries a Stripe payment_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
tokensNo
uploadIdYes
ownerWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ownerWallet
      Added value: +{
+  "type": "string"
+}
  2. Changed7 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 / 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)$"
  3. Changed7 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 / 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)$"
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the flat fee, payment alternatives, the requirement to pass ownerWallet in wallet-less cases, and the polling of preview_status/retry. However, it doesn't specify what happens if unsafe files are found, leaving an outcome ambiguous.

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?

The description is dense but each sentence adds essential information: the core action, pricing, wallet scenarios, and non-extension of lease. It is front-loaded with the main purpose and remains readable despite its length.

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?

Given 4 parameters and no output schema, the description covers the payment flow, wallet condition, and polling process but omits parameter semantics for two fields and the error/response behavior (e.g., what an unsafe file triggers). This leaves gaps an agent must resolve.

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

Parameters2/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. It explains ownerWallet thoroughly ('the address that claimed this slug') and implies uploadId as the zip, but leaves slug and tokens undefined, forcing an agent to guess their roles (e.g., whether tokens affect pricing).

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?

The description states the exact action 'Check the zip for unsafe files, then redeploy the live Worker,' naming the resource (live Worker) and the process (redeploy). It distinguishes itself from siblings like renew ('Does not extend lease days') and publish_website, making its purpose unambiguous.

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?

Provides clear contextual guidance: payment requirements, wallet-less flow, and explicit exclusion that it does not extend lease days. Although it doesn't name alternative tools like renew, the 'does not extend lease' note implicitly directs to that sibling when lease extension is needed.

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

All SORNKan Worldsite 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