Skip to main content
Glama

Cancel analysis job

vestige_job_cancel
Read-only

Cancel a queued or running analysis job and mark it cancelled while keeping already persisted evidence.

Instructions

Cancel a queued or running analysis job. Evidence already persisted is retained and the job becomes 'cancelled'.

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": {
      "jobId": "<jobId>"
    },
    "name": "vestige_job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior1/5

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

The description's disclosure that the job 'becomes cancelled' and that persisted evidence is retained is genuinely useful behavioral context, but cancelling a job mutates server-side state, which directly contradicts the readOnlyHint=true annotation. The definition is therefore self-inconsistent about its side effects, and the mismatch is not merely a nuance an agent could dismiss.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and immediately followed by the two outcomes an agent most needs to know (what is retained, what the new status is). No filler.

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?

For a single-parameter mutation with no output schema, the description covers the essential outcome, but it omits behavior on already-finished jobs, error cases for unknown job IDs, and any note of irreversibility, leaving notable gaps for an operation that changes job lifecycle state.

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?

There is one undocumented parameter (jobId) at 0% schema description coverage, and the description adds no meaning about where the job ID comes from or its expected format, leaving the agent to infer it comes from vestige_analyze or vestige_job_status.

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

Purpose5/5

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

States a specific verb ('Cancel') and resource ('analysis job') plus the scope of eligible jobs ('queued or running'), which distinguishes it from siblings like vestige_job_status and vestige_list_findings at a glance.

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

Usage Guidelines3/5

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

The phrase 'queued or running' implies a precondition for use, but there is no explicit when-to-use guidance, no statement of what happens if the job is already complete, and no reference to alternatives such as monitoring via vestige_job_status instead of cancelling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.