Skip to main content
Glama

sitekick_project_seal

DestructiveIdempotent

Seal the expected project revision for generation.

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>",
      "expected_revision": "<expected_revision>"
    },
    "name": "sitekick_project_seal"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description supplies none of the context those flags demand: what sealing destroys or locks, whether it can be undone, or what occurs on a revision mismatch. It does not contradict the annotations, but for a destructive mutation it adds almost no behavioral signal beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler — but its brevity is under-specification rather than efficiency, and the reader still has to infer the operating model from the schema patterns.

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 need not be explained, but this is a four-parameter destructive mutation with nested payload and zero parameter documentation. A single opaque sentence does not equip an agent to call it safely or know what failure modes to expect.

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 four required parameters, so the description must carry the load. It only gestures at two of them ('project revision'); site_ref and idempotency_key are never mentioned, and no meaning is added about what the expected revision is compared against or how idempotency behaves.

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?

The sentence names a specific verb (Seal) and resource (the expected project revision) with a stated downstream purpose (generation), so the agent knows roughly what it does. However, 'seal' is domain jargon left undefined, and nothing distinguishes this from nearby lifecycle tools such as sitekick_release_prepare or sitekick_release_review.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The phrase 'expected revision' hints at a compare-and-set workflow, but the description never states the condition under which an agent should seal versus prepare, review, or activate.

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