Skip to main content
Glama

Cancel a job

job_cancel
Idempotent

Cancel a queued or running analysis 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": {
      "job_id": "<job_id>"
    },
    "name": "job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesjob_id returned by pcap_analyze

Output Schema

NameRequiredDescriptionDefault
nextNo
errorNo
stageNocurrent stage while running: parsing, audio, sip, ...
job_idYes
statusYes
percentYes
summaryNoset when a PCAP job is done
created_atYes
expires_atNothe result is deleted at this time
finished_atNo
queue_positionNoapproximate place in the queue while queued

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / job_id / description
      Added value: +"job_id returned by pcap_analyze"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutating and repeat-safe nature is covered by structured data. The description adds the state constraint but does not disclose whether cancellation is graceful, what happens to partial artifacts, or what error surfaces when the job cannot be cancelled — meaningful gaps for a mutation tool.

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?

One short, front-loaded sentence with zero filler; the state scope is stated before anything else. It is efficient, though the brevity borders on under-specification rather than tightness.

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?

With an output schema present, return values need no explanation, and the sole parameter is fully documented. However, for a destructive-ish mutation on a job lifecycle, the definition should say more about preconditions and post-cancel state than one sentence provides.

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 100% and the job_id field already states it is 'returned by pcap_analyze', so the description adds no parameter meaning. Baseline 3 applies since the schema does the work for the single parameter.

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 specific verb (cancel) and resource (analysis job) with a qualifier on the target state ('queued or running'), which lets an agent distinguish it from job_status or list_jobs. It does not name a sibling to steer toward, but the action is unambiguous.

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 'queued or running' qualifier implicitly tells the agent this applies only to active jobs, but there is no explicit when-to-use guidance, no statement of what to do for already-completed or failed jobs, and no named alternative for inspecting state first (e.g., job_status).

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