Skip to main content
Glama

cancel_screening_job

Immediately stop a running screening job. Use this if the user made a mistake or the job is no longer needed. Note: Credits for already-processed candidates are not refunded.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesThe ID of the job to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job_id / description
      Previous value: -"The job ID to cancel"New value: +"The ID of the job to cancel."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it usefully discloses two behavioral facts: the stop is immediate and credits for already-processed candidates are not refunded. It does not say whether the action is irreversible, whether the job can be resumed, what state the job ends in, or what happens if the job already finished, leaving 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.

Conciseness5/5

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

Three short sentences with the core action front-loaded, followed by usage and then the cost caveat. Every sentence carries information and none is redundant.

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 one-parameter cancellation tool with no annotations and no output schema, the description covers what it does, when to use it, and the key side effect. It is nearly complete, but an agent still lacks confirmation of irreversibility, resumability, and what an invalid or already-completed job_id yields.

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?

There is a single parameter, job_id, and the schema documents it fully at 100% coverage, so the schema does the work. The description adds no format, sourcing, or validity guidance for the ID beyond what the schema already states.

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, 'Immediately stop a running screening job', which an agent can clearly tell apart from status or audit operations on the same resource. It stops short of naming a sibling, so it is clear but relies on the agent to infer the contrast with get_screening_status or audit_screening_job.

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?

'Use this if the user made a mistake or the job is no longer needed' gives concrete triggering conditions for invocation. It does not state when NOT to use it or point to any alternative for pausing, restarting, or inspecting a job instead.

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