Skip to main content
Glama
Sign In
genieacs-mcp

genieacs-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Retry faulted task

retry_task
Idempotent

Clear the fault on a faulted task so the device reruns it at its next session. Check the fault reason first; an unchanged cause will fault again.

Instructions

Run a faulted task again: GenieACS clears the task's fault, and the device runs the task at its next session. Read genieacs://faults/{device_id} first to see why it failed; retrying a task whose cause is unchanged faults again. A task that has not faulted is left as it is. Example: retry_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": "retry_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe faulted task's _id, from genieacs://tasks/{device_id}.

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 faulted task's _id, from genieacs://tasks/{device_id}."
    • addedInput schema / properties / task_id / minLength
      Added value: +1
  2. Addedv0.3.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds genuinely non-structured behavior: the task is not executed immediately but at the device's next session, and the fault flag is cleared. It doesn't describe what the call returns or how failures at retry time surface, which keeps it short of a 5.

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 sentences: behavior first, prerequisite and pitfall second, example last. Nothing is repeated from the schema or annotations, and every sentence contributes actionable information.

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 mechanism, timing, prerequisite lookup, and the no-op case for non-faulted tasks. The only real gap is what a successful or failed invocation returns, which for an agent verifying the retry outcome would be useful.

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% and the single parameter is already documented as the task's _id from genieacs://tasks/{device_id}, so the baseline is 3. The description adds a concrete example value showing the expected ObjectId-like string format, which is modest but real added meaning.

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?

Opens with a specific verb+resource ('Run a faulted task again') and immediately explains the mechanism: GenieACS clears the fault and the device runs the task at its next session. This makes it clearly distinct from siblings such as delete_task or connection_request, which act on the device or task list rather than on a fault state.

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 tells the agent to read genieacs://faults/{device_id} first to diagnose the cause, and warns that retrying with an unchanged cause will fault again — a clear when-not-to-use condition. It also states that a non-faulted task is left as it is, closing the remaining ambiguity about safe invocation.

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