Skip to main content
Glama
Sign In
genieacs-mcp

genieacs-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Delete queued task

delete_task
DestructiveIdempotent

Remove a queued or faulted GenieACS task before the device runs it, such as an accidental firmware download, reboot, or a faulted task you do not want retried.

Instructions

Remove a task from the GenieACS queue before the device runs it, for example a firmware download or reboot queued by mistake, or a faulted task you do not want retried. GenieACS already deletes a task once the device has run it, so every task you can see in genieacs://tasks/{device_id} is either waiting or faulted. Fails with ACS error 503 while the device is in a session with GenieACS; try again a few seconds later. Use retry_task instead to run a faulted task again. Example: delete_task(task_id="67abc123def4560012345678").

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task's _id, from genieacs://tasks/{device_id} or from the task_id a task tool returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / task_id / description
      Previous value: -"The task identifier (_id field from the task document). Obtain task IDs from the genieacs://tasks/{deviceId} resource."New value: +"The task's _id, from genieacs://tasks/{device_id} or from the task_id a task tool returned."
    • addedInput schema / properties / task_id / minLength
      Added value: +1
  2. Addedv0.3.3

TDQS

A4.7/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, yet the description adds real operational context the annotations cannot: a 503 while the device is in session, and the model that GenieACS auto-deletes completed tasks so every visible task is waiting or faulted. It stops short of explicitly saying the removal is permanent and unrecoverable, which would close the loop on the destructive hint.

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?

Front-loaded with the verb and scope, then layered: what visible tasks mean, the failure mode, the alternative tool, and an example. Every sentence carries distinct information with no restatement of the title or schema.

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

Completeness5/5

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

A single-parameter delete with no output schema; the description covers scope, state semantics, transient errors, and the sibling alternative. Nothing an agent needs in order to invoke it correctly is missing.

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?

Schema coverage is 100%, so 3 is the baseline; the description goes beyond it by adding a concrete example call with a realistic 24-hex ObjectId format for task_id. That format hint is genuinely useful for constructing a valid identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove a task from the GenieACS queue') plus the precise condition that makes it applicable (before the device runs it). It also implicitly separates itself from retry_task by naming it, so an agent can pick between the two without opening schemas.

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

Usage Guidelines5/5

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

Explicitly names the alternative tool ('Use retry_task instead to run a faulted task again') and gives concrete when-to-use scenarios (firmware download or reboot queued by mistake). It even covers the transient failure case and tells the agent to retry a few seconds later.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools