Komers Sites

Publish site

publish_site

Make the current draft live. Costs 5 credits per 30 days of hosting (charged now if not already paid up; renews automatically).

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": {
      "site": "<site>"
    },
    "name": "publish_site"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Site slug (e.g. "kopitiam-muar") or id

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, open-world write. The description adds genuinely new behavior: a 5-credit cost per 30 days, immediate charge if unpaid, and automatic renewal — exactly the side effects an agent must surface before calling. It stops short of stating reversibility (unpublish/rollback) or failure modes such as insufficient credits.

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?

Two short sentences, action first, billing second, with zero filler. Each sentence carries information the agent cannot get from structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter publish action with a complete schema, the definition covers the essential cost and renewal behavior. The only real gap is guidance on the companion tools (preview before publishing, unpublish/rollback after), which slightly limits routing confidence.

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% and the single 'site' parameter already documents slug-or-id with an example, so the description adds no parameter meaning. Baseline 3 applies.

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 ("Make the current draft live") that pins the scope to the current draft rather than a named published version, which cleanly separates it from preview_site, rollback_site, and unpublish_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended moment of use (draft is ready to go live) is implied by the wording, but no alternatives are named — an agent isn't told when to prefer preview_site first or when unpublish_site/rollback_site are the appropriate follow-ups.

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

All Komers Sites tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?