Skip to main content
Glama
timeplus-io

mcp-timeplus

by timeplus-io

explore_kafka_topic

Retrieve messages from a specified Kafka topic to inspect streaming data. Optionally limit the number of messages returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes
message_countNo

Implementation Reference

  • The main handler function for the explore_kafka_topic tool. It consumes messages from a Kafka topic using the confluent_kafka Consumer, returns parsed JSON messages.
    @mcp.tool()
    def explore_kafka_topic(topic: str, message_count: int = 1):
        logger.info(f"Consuming topic {topic}")
        conf = json.loads(os.environ['TIMEPLUS_KAFKA_CONFIG'])
        conf['group.id'] = f"mcp-{time.time()}"
        client = Consumer(conf)
        client.subscribe([topic])
        messages = []
        for i in range(message_count):
            logger.info(f"Consuming message {i+1}")
            message = client.poll()
            if message is None:
                logger.info("No message received")
                continue
            if message.error():
                logger.error(f"Error consuming message: {message.error()}")
                continue
            else:
                logger.info(f"Received message {i+1}")
                messages.append(json.loads(message.value()))
        client.close()
        return messages
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on FastMCP instance in mcp_server.py
    @mcp.tool()
    def explore_kafka_topic(topic: str, message_count: int = 1):
  • Import of the confluent_kafka Consumer class used by explore_kafka_topic
    from confluent_kafka import Consumer
  • Input parameters: topic (str, required) and message_count (int, default 1) define the schema for this tool
    def explore_kafka_topic(topic: str, message_count: int = 1):
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/timeplus-io/mcp-timeplus'

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