Skip to main content
Glama

sitekick_adoption_capture

DestructiveIdempotent

Request an existing-site capture using the exact assessment hash and original idempotency key. Follow the returned WordPress continuation and explicitly confirm with an owner browser session; this does not publish.

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

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
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description adds real context beyond them: the capture does not publish, and the result must be confirmed through an owner browser session, which is an authorization/ownership requirement the annotations cannot express. It still leaves unstated what the destructive effect actually touches on the live site.

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 dense sentences with the resource and its input constraint front-loaded, then the follow-up steps. Nothing is padding, though the compressed phrasing ("WordPress continuation") relies on the agent inferring a fair amount from prior tool outputs.

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

Completeness4/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, and the description covers the key risks an agent needs — idempotent replay with the original key, owner-session confirmation, and no publishing. It is somewhat thin on prerequisites for site_ref (what state the site must be in) given a destructive, open-world operation.

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%, so the description has to carry the load, and it only covers two of the three inputs — mandating that assessment_hash be the exact hash and idempotency_key the original key. The required site_ref parameter and the regex-constrained formats are left entirely to the schema, so it adds partial meaning only.

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?

States a concrete verb and resource — requesting a capture of an existing site — and ties it to two specific inputs (the exact assessment hash and the original idempotency key). It does not name a sibling such as sitekick_site_existing_select or sitekick_site_inspect to distinguish the capture step from selection/inspection, so it falls short of a 5.

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?

"the exact assessment hash and original idempotency key" implies this runs after an assessment and is safe to retry with the same key, and "Follow the returned WordPress continuation and explicitly confirm with an owner browser session" gives the required post-call sequence. No explicit when-not-to-use or named alternative is given, so it stops at a clear context without exclusions.

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