Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_cancel_job

DestructiveIdempotent

Request cancellation of a company-owned standalone job that has not started. Use job_id returned by skavio_submit_job or skavio_list_jobs; a standalone job is not part of a bulk run or workflow. Returns the job state and refreshes local accounting. Running or already finished jobs may reject cancellation; accepted running work can finish and charge, so inspect skavio_get_job afterward. This is a state-changing operation requiring processing permission, not deletion of results. Use skavio_cleanup only for expired local result copies.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesID of a job owned by the authenticated company, copied from skavio_submit_job.id or skavio_list_jobs.jobs[].id. Preserve it exactly; foreign or unknown IDs fail. For downloads the job must be completed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Arguments for skavio_cancel_job. Company and permissions come from the authenticated connection."
    • addedInput schema / properties / job_id / description
      Added value: +"ID of a job owned by the authenticated company, copied from skavio_submit_job.id or skavio_list_jobs.jobs[].id. Preserve it exactly; foreign or unknown IDs fail. For downloads the job must be completed."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already flag destructive, idempotent, and non-read-only behavior, and the description adds substantial behavior that the annotations do not cover: it is state-changing, it requires processing permission, running or finished jobs may reject the cancellation, accepted running work can still finish and charge, and it is not a result deletion. That is exactly the extra context an agent needs before invoking a mutation.

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?

The description is front-loaded with the purpose and then the behavioral caveats, and it reads efficiently. A small amount of redundancy appears where the sentence about the source of job_id restates the schema's own wording.

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?

No output schema exists, yet the description still states what the call returns (the job state, with local accounting refreshed). With annotations covering the safety profile and the single parameter fully documented, nothing needed to call the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description largely repeats the schema's guidance on preserving job_id exactly. It does add one piece of semantics that the schema does not state: the ID must refer to a standalone job rather than a bulk run or workflow member, which narrows what counts as a valid argument.

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 names a specific verb and resource (cancel a job), and it scopes that resource narrowly to company-owned standalone jobs that have not yet started. It explicitly rules out bulk runs and workflows, so the agent can distinguish this from siblings like skavio_cleanup and skavio_get_job.

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

Usage Guidelines5/5

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

The description tells the reader where to get the ID (skavio_submit_job or skavio_list_jobs) and names the follow-up (skavio_get_job) for verifying the outcome. It also routes skavio_cleanup to the different case of expired local result copies, which gives explicit when-not guidance.

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

All Skavio PDF, OCR & Document Processing MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources