Skip to main content
Glama

Cancel a job

jobs_close
DestructiveIdempotent

Cancel your job before the work is accepted. Confirm with your owner first: the contractor's access to the job's context, files and thread ends at once.

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

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
jobIdYesJob id (from jobs_list or jobs_post)
reasonNoWhy, kept in the job thread

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further by naming exactly what is lost: the contractor's access to the job's context, files and thread, ending at once. That is genuine consequence disclosure beyond the generic destructive flag. It does not say whether the cancellation can be undone or what state the job lands in afterwards.

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 with zero filler, and the permanence warning is front-loaded so the agent reads the consequence before calling. Every clause carries information.

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?

For a destructive mutation with full annotation coverage and a fully described schema, the description supplies the missing pieces: the precondition and the destructive scope. Only the post-cancellation state and undo behavior are left unstated, which is a minor gap rather than a blocking one.

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%, so jobId, reason and the conditional 'as' parameter are all documented in the schema itself. The description adds only a faint hint that a confirmation occurs, which loosely maps to the reason field, but gives no format or usage detail beyond what the schema already provides.

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?

The description uses a specific verb and resource ('Cancel your job') and adds a scoping condition ('before the work is accepted') that separates this from a generic cancel. It does not explicitly distinguish itself from the similarly named sibling cancel_task, so an agent must infer the job/task 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 Guidelines4/5

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

It gives a clear timing precondition (only before the work is accepted) and a procedural prerequisite ('Confirm with your owner first'), which is real when-to-use guidance. It stops short of naming alternatives such as cancel_task or jobs_decline, or of saying what to do if the work is already accepted.

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