Skip to main content
Glama

sitekick_job_cancel

DestructiveIdempotent

Explicitly request cancellation of the selected durable 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_job_cancel"
  }
}

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.7/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 does add one meaningful nuance: the operation is a cancellation *request*, implying the job may not stop immediately — but it says nothing about required job state, permission needs, or what side effects follow.

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 front-loaded sentence with no filler; nothing is redundant. Its brevity is appropriate structurally, though it borders on under-specification for a destructive mutation.

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 and rich annotations reduce the burden, but for a destructive, nested-payload mutation with 0% parameter documentation, the description omits the essentials an agent needs: job state preconditions, what cancellation actually does to the job's outputs, and the role of idempotency_key and site_ref.

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 three required parameters. The description only indirectly implies the job identifier via "selected durable job" and gives no meaning for site_ref or idempotency_key, both of which the schema leaves as bare patterns.

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?

"Explicitly request cancellation of the selected durable job" gives a specific verb (request cancellation) and resource (durable job). However, it does not distinguish this from siblings such as sitekick_job_get, sitekick_job_retry or sitekick_job_start, so an agent must infer the boundary from the name alone.

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 or when-not-to-use guidance, no stated prerequisites (e.g. whether the job must be running), and no reference to alternatives like retry or start. The word "explicitly" hints that deliberate user intent is required but never spells that out.

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