Skip to main content
Glama

Cancel job in CrewNest

crewnest_cancel_job
Read-onlyIdempotent

Cancel job in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crewnest_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false. The description earns credit beyond them by explicitly stating it 'opens nothing by itself' and by disclosing the shape of its return value (screens, buttons, fields), which resolves the name/behavior tension. It does not mention account scoping enforcement or failure modes when the job is not cancellable.

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 instruction is front-loaded and useful, but the final sentence about CrewNest's official Job Pricing MCP server and its three read-only tools is unrelated to cancelling a job and injects noise into tool selection. The middle sentence is a semicolon-chained run-on that mixes the read-only guarantee with the next-step routing.

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 zero-parameter, no-output-schema tool, the definition covers what an agent needs: it is read-only, it yields step-by-step UI instructions, and it hands off to browser tools for execution. The only gap is the absence of any note on what happens if the job cannot be cancelled or which account context applies.

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?

Zero parameters, so semantics baseline is 4. Nothing extra is required, and the description correctly implies the target job is identified later during the browser-driven flow rather than via a tool argument.

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 names a specific verb (cancel) and resource (job) but immediately reframes the tool as a guidance generator: it 'Returns how to do it in CrewNest step by step (screens, buttons, fields)'. That contrast with the tool name is genuinely useful, though an agent must read past the first clause to learn the tool does not itself cancel anything.

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?

Clear routing: use this to obtain the steps, then execute them 'with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'. It lacks discrimination against the closest in-family alternative (crewnest_update_job_status), so an agent still has to infer whether cancelling is a status change or a separate flow.

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