Skip to main content
Glama

Skip a task

abort_task
DestructiveIdempotent

Skip an armed task: not this time; the loop moves on. The task is unarmed and its abortions count goes up by 1. On a task that is not armed it changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task's id (from list_tasks, todays_tasks or a loop's tasks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to say what is destroyed and how repeat calls behave. It does both: the task is unarmed, its abortion counter increments by one, and a call against an unarmed task is a no-op, which also explains why repeated calls stay idempotent. Return value and any permission or loop-state requirements are not covered.

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, front-loaded with the action and its consequence, then the counter effect, then the no-op case. Nothing is repeated or padded.

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 single-parameter mutation with no output schema, the description covers the precondition, the state change, the side effect, and the null case, which is nearly everything an agent needs. The only gap is what the call returns, which nothing else in the definition supplies.

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 task_id's description already names where the id comes from (list_tasks, todays_tasks, loop tasks). The prose adds no further meaning about the single parameter, so the baseline of 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?

"Skip an armed task" gives a concrete verb and resource, and "the loop moves on" clarifies the semantic effect beyond the tool name. It defines its scope (armed tasks) precisely but never names a sibling such as dequeue_task or update_task to contrast with, so sibling differentiation is left implicit.

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?

The precondition is explicit — the task must be armed — and the closing sentence states the negative case: on an unarmed task nothing changes. What is missing is routing advice to an alternative tool when the task is not armed or when a different state change is wanted.

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