Skip to main content
Glama

Plures

Cancel a human task

cancel_human_task
DestructiveIdempotent

Cancel a task that is still waiting for answers, for example when the decision no longer matters. Answers already given are still billed.

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>"
    },
    "name": "cancel_human_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task_id ask_humans returned

Output Schema

NameRequiredDescriptionDefault
kindNo
meanNo
modeYes
labelYes
routeYes
votesYes
answerYes
statusYes
answersYes
reasonsNo
signoffNo
task_idYes
agreementYes
contestedNo
with_teamYes
decided_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the mutation/idempotency profile is structured data. The description still adds genuinely non-obvious context with "Answers already given are still billed," a cost consequence the annotations cannot express. It omits what happens if the task is already answered or completed (error vs. no-op), which is the main remaining behavioral gap.

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?

Two short sentences with the action and scope front-loaded and the billing caveat as a trailing warning, which is the right order. Every clause carries information; no filler.

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?

With one required parameter, an output schema, and rich annotations, the description covers purpose, a usage scenario, and a billing consequence adequately. Only the already-answered/terminal-state behavior and error conditions are unaddressed.

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?

Schema coverage is 100% and the single task_id parameter is documented as "The task_id ask_humans returned," tying it to the producing sibling. The description adds no further meaning about the identifier, but the schema already carries the load, so baseline 3 applies.

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 a precisely scoped resource ("a task that is still waiting for answers"), which implicitly separates it from get_human_answer, the sibling for retrieving answers already given. It stops short of naming that sibling, so differentiation relies on the agent reading the scope clause.

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?

Provides a concrete when-to-use condition: "for example when the decision no longer matters." There are no explicit exclusions or prerequisites stated (e.g., what to do if the task already has an answer), so the agent must infer the boundary case.

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.