AKHQ MCP Server

get_connect_task_restart

Read-onlyIdempotent

Restart a specific Kafka Connect task by providing cluster, connect ID, connector name, and task ID to resolve failures and resume data streaming.

Instructions

Restart a specific connector task

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": {
      "cluster": "<cluster>",
      "connectId": "<connectId>",
      "name": "<name>",
      "taskId": "<taskId>"
    },
    "name": "get_connect_task_restart"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Connector name
`taskId`	Yes	Task ID
`cluster`	Yes	Cluster name
`connectId`	Yes	Connect cluster ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The description says 'Restart a specific connector task', which is a state-changing operation, yet annotations declare readOnlyHint=true and idempotentHint=true. This is a direct contradiction; the description provides no disclosure of side effects, restart semantics, or consequences, so an agent would be actively misled.

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?

The description is a single, efficient sentence with no filler. It front-loads the core action and resource, and every word earns its place.

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 restart operation with no output schema and contradictory annotations, the description is incomplete. It does not explain what happens to the task, whether the restart is synchronous, or what response to expect, and the readOnly contradiction undermines the agent's ability to reason about the operation safely.

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 description coverage is 100%, and every parameter has a basic description in the schema. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies. It does not clarify the relationship between 'cluster' and 'connectId', but the schema already names both.

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?

The description uses a specific verb ('Restart') and resource ('specific connector task'), making the operation clear. It differentiates at the resource level from sibling get_connect_restart, which targets a connector rather than a task, though it does not explicitly name the alternative.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives such as get_connect_restart or get_connect_tasks. The description states the action but does not mention prerequisites, exclusions, or conditions that would help an agent choose between related connector/task operations.

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

Deploy Server