Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

jobs_id_cancel_post

Cancel a queued job by ID before it starts; running, finished, expired, or already cancelled jobs remain unchanged.

Instructions

jobs: Cancel a job. POST /v1/jobs/{id}/cancel. Cancels a job that is still queued. A running, finished, expired or already cancelled job is unchanged. Cancelling costs 0 credits. Costs 0 credits when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "id": "<id>"
    },
    "name": "jobs_id_cancel_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id from the 202 response. Pass that id and nothing else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses that only queued jobs change, other states are unchanged, and cancellation costs 0 credits. It does not describe authentication requirements or the response body, but it adds substantial behavioral detail beyond the schema.

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

Conciseness3/5

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

The core purpose and state constraint are front-loaded, but the cost explanation is repetitive: 'Cancelling costs 0 credits' is immediately followed by 'Costs 0 credits when it succeeds' and then several overlapping zero-cost cases. The description could be shortened without losing meaning.

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 simple one-parameter cancellation tool with no annotations and no output schema, the description covers the key calling conditions, state behavior, and cost model. It is mostly complete, though it does not mention the response shape or any permission requirements.

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?

The input schema already documents the single id parameter at 100% coverage, including its source from the 202 response. The description does not add any further meaning about the parameter, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: cancel a job, with the exact endpoint POST /v1/jobs/{id}/cancel. It also distinguishes the target state by saying only a still-queued job can be cancelled, which clearly differentiates this from a generic job lookup such as jobs_id.

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 gives clear when-to-use and when-not-to-use guidance: use it for a queued job, and expect no effect for running, finished, expired, or already cancelled jobs. It does not explicitly name an alternative tool, but the state-based conditions are sufficiently clear for selection.

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