Skip to main content
Glama
Sign In
Pulsar MCP Server

Pulsar MCP Server

by Germain-D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pulsar_consume

Consume messages from a Pulsar topic by specifying the topic and subscription name, with an optional limit on the number of messages.

Instructions

Consume messages from a Pulsar topic

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": {
      "topic": "<topic>",
      "subscription_name": "<subscription_name>"
    },
    "name": "pulsar_consume"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe Pulsar topic to consume from
max_messagesNoMaximum number of messages to consume
subscription_nameYesThe subscription name for consuming messages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description fails to disclose important behavioral traits such as whether messages are acknowledged, if consumption is blocking/non-blocking, or any side effects on the subscription. For a consume operation, these details are critical.

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 a single, concise sentence with no waste. However, it could be improved by front-loading key details such as blocking behavior or subscription durability.

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?

Despite the high schema coverage, the description lacks completeness for a consumption tool. There is no output schema, and the description does not explain return values (e.g., message contents), termination conditions, or error scenarios. It is insufficient for an agent to fully understand tool behavior.

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?

The input schema has 100% description coverage, so the schema already explains each parameter. The tool description 'Consume messages from a Pulsar topic' adds no additional meaning beyond the schema, meeting the baseline for high schema coverage.

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?

The description 'Consume messages from a Pulsar topic' clearly states the verb 'consume' and the resource 'messages from a Pulsar topic'. It effectively distinguishes from sibling tools like pulsar_publish and pulsar_create_topic.

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?

No guidance on when to use this tool versus alternatives (e.g., when to use pulsar_publish instead). It lacks context about prerequisites or exclusions, leaving the agent to infer usage.

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