Skip to main content
Glama

sitekick_release_review

DestructiveIdempotent

Prepare a publication review. Human approval requires the returned browser continuation and an actual owner session.

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

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.5/5.0
Behavior3/5

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

The annotations already disclose destructive=true, openWorld=true, idempotent=true, so the safety profile is covered. The description adds genuinely new context beyond them: approval is human gated and requires a returned browser continuation plus an actual owner session. It still omits what state is created or destroyed and what happens on retry, which matters for a destructive mutation.

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 short, front-loaded sentences with no filler. The problem is under-specification rather than verbosity, so it is efficient but insubstantial for a tool of this complexity.

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

Completeness2/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 are fairly covered, but for a destructive, dual-mode mutation the description omits the intent variants, the effect on release generation, and how the human-approval continuation is obtained. An agent could not call this correctly from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% on three required parameters, and the payload is a oneOf with two entirely different shapes (release activation vs campaign promotion/undo). The description says nothing about payload variants, site_ref, or idempotency_key, so it does not compensate for the coverage gap at all.

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 a publication review' gives a verb and a resource, but it is thin: the tool actually mutates release/campaign state in two different modes (activate/rollback and promote/undo) and the description never says so. It does not distinguish itself from nearby siblings such as sitekick_release_review_get or sitekick_release_preview.

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 only usage-shaped sentence is a prerequisite about human approval requiring a browser continuation and an owner session. There is no statement of when to call this versus sitekick_release_preview, sitekick_release_activate, or sitekick_release_review_get, and no exclusions or preconditions on release state.

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