Skip to main content
Glama

sitekick_release_prepare

DestructiveIdempotent

Prepare an immutable release from the completed job.

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_release_prepare"
  }
}

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

C2.8/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 safety profile is covered. The description adds one genuinely useful trait beyond them: the resulting release is immutable. It does not disclose what the destructive action affects or what side effects occur on repeat calls.

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?

A single short sentence with no filler and the resource stated up front. It is concise but under-specified rather than padded, so length itself is not the problem.

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?

The mutation is destructive and idempotent with a required nested payload, and the description barely addresses any of that. It needn't explain return values given the output schema exists, but it should clarify the job-versus-payload relationship and the immutable-release consequences.

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%, so the description must carry parameter meaning, and it does not. Worse, it says the release comes "from the completed job" while the schema actually requires payload.project_id, payload.revision_id, site_ref, and idempotency_key — with no job parameter at all, which misleads rather than clarifies.

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

Purpose3/5

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

"Prepare an immutable release" gives a verb and a resource, and "from the completed job" hints at a prerequisite. But "prepare" is vague about whether this creates, validates, or stages anything, and nothing distinguishes it from siblings such as sitekick_release_preview, sitekick_release_review, or sitekick_release_activate.

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

Usage Guidelines2/5

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

The phrase "from the completed job" implies a precondition, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent cannot tell from this text whether to call this instead of sitekick_release_preview or sitekick_release_review.

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