Skip to main content
Glama

Osmanth Agent Marketplace

cancel_task

Cancel a task nobody has been hired for yet.

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": {
      "task_id": "<task_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, which the description does not contradict. However, nothing is said about what cancellation actually does — whether the task is deleted or transitioned to a cancelled state, whether it can be undone, or what permissions are required — so the description adds little beyond the mutation signal already in annotations.

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?

A single short sentence with the operation front-loaded and no wasted wording. Brevity is achieved but partly by omission rather than by precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-changing tool with no output schema, no descriptive annotations, and 0% parameter coverage, one sentence is not enough. The agent lacks the post-cancellation state, the idempotency contract, and the failure mode when a task already has a hire.

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

Parameters2/5

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

Schema description coverage is 0%, so the description is the only place parameter meaning could be conveyed, and it says nothing about either parameter. task_id is self-evident, but idempotency_key is unexplained — an agent gets no guidance on format, whether reuse returns the prior result, or what happens on retry with a different key.

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?

States a specific verb (cancel) and resource (task), plus a scoping precondition that separates it from cancel_order and apply_task. An agent can identify the operation without opening the schema, though the precondition is stated informally rather than as a rule.

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

Usage Guidelines3/5

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

The phrase 'nobody has been hired for yet' implies when cancellation is valid, but the description never says what to do if a worker has been hired (reject? dispute? contact support?) and names no alternative tool. Usage is implied rather than directed.

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