Skip to main content
Glama

sitekick_project_create

DestructiveIdempotent

Create an explicit SiteKick design project from a complete blueprint, optionally refining an existing release. For native WordPress generation preserving custom themes/plugins, use workspace.write with action plan.

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>",
      "site_ref": "<site_ref>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the bar is lower, but the description adds no context about what destruction means here (overwriting an existing project or release, or conflicting with a prior revision) or how the idempotency key is expected to behave. Beyond the scope stated by the annotations, the only added context is that a complete blueprint is needed and that refinement of an existing release is optional.

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 sentences, zero padding, with the core action front-loaded and the routing caveat placed second where it belongs. Every clause earns its place.

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 no explanation, but the input is a large oneOf with two payload branches and only one is described. Redirecting native WordPress generation to workspace.write while the schema still accepts a native_campaign payload leaves an agent uncertain which path this tool actually supports, and blueprint requirements (schema_version, mandatory navigation/style/bindings) are unmentioned.

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 0% across only 3 parameters, so the description must compensate, and it partly does: "complete blueprint" maps to payload.blueprint and "refining an existing release" maps to the payload.refinement branch. It says nothing about site_ref or idempotency_key, and it never mentions the alternate native_campaign payload shape the schema accepts, which leaves the largest branch of the input undocumented.

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 ("Create an explicit SiteKick design project"), the required input ("from a complete blueprint"), and the optional variant ("optionally refining an existing release"). It also names a sibling tool (workspace.write) for the case it does not cover, so an agent can separate the two without opening either schema.

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?

Gives an explicit routing rule: native WordPress generation that preserves custom themes/plugins should go through workspace.write with an action plan. However, it says nothing about when to prefer project_create over the adjacent siblings project_update, project_estimate, or project_get, and it does not state the prerequisite that the blueprint must already be complete.

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