Skip to main content
Glama
Sign In

SiteKrs

by io.github.hansail001
OverviewDiscussionsAdmin

Open a SiteKrs template

create_site

Return the SiteKrs editor URL for a chosen catalog template. Does not download or read template ZIP files. For user-authored source, do not call this tool: tell the user to open the returned import_url and use the existing Import Template dialog (folder or ZIP).

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": {
      "template_id": "<template_id>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesTemplate id returned by list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds useful scope limits, especially that it does not download or read template ZIP files, but it does not explain what non-read-only side effect occurs or clarify the 'import_url' reference despite returning an editor URL.

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 purpose is front-loaded and the description is only three sentences with no wasted padding. However, the phrase 'open the returned import_url' is slightly confusing because the tool is described as returning an editor URL, not an import_url.

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?

For a one-parameter tool with annotations and no output schema, the description gives enough to call it correctly in the catalog-template case. It remains incomplete about the actual return shape and the non-read-only side effect, and the import_url reference creates ambiguity about what is returned.

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 coverage is 100%, so the single template_id parameter is already documented as coming from list_templates. The description adds only the phrase 'chosen catalog template' and does not add format, constraints, or selection details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and result: return the SiteKrs editor URL for a chosen catalog template. It clearly distinguishes this from template ZIP handling and from user-authored source. It does not explicitly name the sibling list_templates, but the purpose is still easy to identify.

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?

The description gives an explicit when-not-to-use case: for user-authored source, do not call this tool and instead direct the user to the Import Template dialog. The positive case is clear but slightly implied through 'chosen catalog template' rather than stated as a direct when-to-use rule.

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

All SiteKrs toolsInspect
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