Skip to main content
Glama
BhaumikAbhishek

OCI Kafka MCP Server

oci_kafka_reset_consumer_offset

Reset consumer group offsets to earliest, latest, or a specific offset for a topic. Requires empty group and enabled writes.

Instructions

Reset consumer group offsets for a topic. THIS IS A DESTRUCTIVE OPERATION.

The consumer group must have no active members (EMPTY state). Requires --allow-writes to be enabled. This is a HIGH RISK operation that requires confirmation.

Args: group_id: The consumer group ID to reset offsets for. topic_name: The topic to reset offsets for. strategy: Reset strategy — 'earliest' (beginning), 'latest' (end), or a specific integer offset. partition: Optional specific partition number. If omitted, resets all partitions.

Returns the reset status and new offset positions for each partition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes
strategyNolatest
partitionNo
topic_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Without annotations, the description carries full burden. It labels the operation as 'DESTRUCTIVE' and 'HIGH RISK', explains the empty consumer group requirement, and notes the need for confirmation. This provides strong transparency, though it could elaborate on the exact impact on consumer offsets.

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

Conciseness4/5

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

The description is reasonably concise, front-loading the purpose and warning, then prerequisites, then parameter descriptions. It is efficient without being overly terse.

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?

Given the tool's complexity (destructive, prerequisites, multiple parameters), the description covers prerequisites, parameter meanings, and return summary. The presence of an output schema means return values need not be detailed further. It is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining each parameter: group_id, topic_name, strategy (with examples of options), and partition (optional, default behavior). This adds significant value beyond the schema.

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?

Description clearly states 'Reset consumer group offsets for a topic', specifying a precise verb and resource. It is distinct from all sibling tools, none of which perform a reset operation.

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?

Description provides explicit prerequisites (empty consumer group, allow-writes enabled) and risk level. It does not explicitly mention when not to use the tool, but given no alternative reset tool exists, the guidelines are clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BhaumikAbhishek/oci-kafka-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server