Skip to main content
Glama
Sign In
Pulsar MCP Server

Pulsar MCP Server

by Germain-D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pulsar_publish

Publish a message to a Pulsar topic, optionally adding key-value properties.

Instructions

Publish a message to 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>",
      "message": "<message>"
    },
    "name": "pulsar_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe Pulsar topic to publish to
messageYesThe message content to publish
propertiesNoOptional message properties as key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states the basic function without revealing idempotency, error handling, or side effects. Does not mention required permissions or message delivery guarantees.

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 concise (one sentence) but lacks structure. It is not overly verbose, yet sacrifices completeness for brevity.

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?

Given no output schema and 3 parameters including a nested object, the description fails to explain return values, error conditions, or usage nuances. For a publish tool, critical information like whether a message ID is returned is missing.

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%, so parameters are already documented. The description adds no additional meaning beyond the schema, achieving the baseline of 3.

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 the action ('publish a message') and the resource ('Pulsar topic'), effectively distinguishing from siblings like pulsar_consume. The verb-noun combination is specific and 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?

No guidance is provided on when to use this tool versus alternatives (e.g., pulsar_consume), no prerequisites mentioned, and no conditions for appropriate use. The description lacks any usage context.

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