Skip to main content
Glama
Sign In
llm-cli-gateway

llm-cli-gateway

by verivus-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

llm_job_cancel

DestructiveIdempotent

Cancel a running gateway async or deferred-sync job by its job ID to halt unwanted operations and free system resources.

Instructions

Cancel a running gateway async or deferred-sync job by jobId.

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": "llm_job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesAsync job ID from *_request_async

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.16.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds that the tool cancels 'running' jobs and applies to 'gateway async or deferred-sync' jobs, providing useful context beyond the annotations.

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?

The description is a single, clear sentence with no extraneous information, efficiently conveying the tool's purpose and required parameter.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one parameter, no output schema, and comprehensive annotations, the description adequately covers all necessary details for correct invocation.

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 coverage is 100% for the single required parameter jobId, and the description merely repeats 'by jobId' without adding additional semantics beyond the schema's description.

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?

The description clearly states the verb 'Cancel', the resource 'gateway async or deferred-sync job', and the method 'by jobId'. It distinguishes this tool from sibling read-oriented tools like job_status and job_result.

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 description implies usage when a job needs to be stopped, but does not explicitly state when not to use it or suggest alternative tools for checking job state first.

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

Deploy Server

Other Tools