Skip to main content
Glama

sitekick_site_create

DestructiveIdempotent

Create a site using the original idempotency key. Reuse that key when explicitly recovering an uncertain creation.

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": {
      "payload": "<payload>",
      "create_target": "<create_target>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_site_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
create_targetYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuine meaning beyond them by tying the idempotency key to retry-after-uncertainty behavior, but it says nothing about what a successful creation produces, what gets created (name only?), or what a duplicate key returns.

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?

Two tight sentences with the verb front-loaded and no filler. The second sentence is a useful constraint rather than padding, though the phrasing "explicitly recovering an uncertain creation" is slightly abstract.

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?

An output schema exists, so return values need not be explained. But for a destructive, open-world mutation with a nested payload and a required discriminator, the description is thin on preconditions and on what a duplicate-key retry actually returns.

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 description coverage is 0% across three required parameters. The description only touches one of them (idempotency_key) and even there adds no format or scoping detail; payload.name and the create_target.kind discriminator are left entirely to the schema's const/pattern constraints.

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 resource ("Create a site") that separates it from read/select siblings like sitekick_site_existing_select. It does not differentiate itself from the other create tools in the family (project_create, template_create), which is the main gap.

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?

It gives real but narrow guidance on one action: reuse the idempotency key when recovering an uncertain creation. It never states the normal when-to-use condition, prerequisites, or when a sibling create/select tool would be the better choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources