Skip to main content
Glama
Sign In
AKHQ MCP Server

AKHQ MCP Server

by seb-noirot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_connect_resume

Read-onlyIdempotent

Resume a paused Kafka Connect connector to restore data flow. Provide the cluster, Connect cluster ID, and connector name to reactivate it.

Instructions

Resume a connector

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

Input Schema

NameRequiredDescriptionDefault
nameYesConnector name
clusterYesCluster name
connectIdYesConnect cluster ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

The description says 'Resume a connector', which implies a state-changing control operation, but annotations declare readOnlyHint=true. This is a direct contradiction. No context is provided about side effects, permissions, or return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief and front-loaded, but it omits helpful context such as what state the connector transitions to or how it relates to pause/restart. It is concise to the point of being under-specified.

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?

With no output schema and minimal context, the description leaves out what a successful resume returns, whether the connector must be paused first, and whether there are side effects. The annotation contradiction further undermines completeness.

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 each parameter has a clear schema description. The tool description itself adds no parameter semantics, but the schema already handles this sufficiently, 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?

The description uses the specific verb 'Resume' with the resource 'connector', clearly identifying the action. It does not explicitly differentiate from sibling tools like get_connect_pause or get_connect_restart, but the core semantics are unambiguous.

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 on when to call this tool versus alternatives. It does not mention prerequisites such as the connector needing to be paused, nor does it reference related sibling operations like get_connect_pause or get_connect_restart.

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