Skip to main content
Glama
Sign In
Pulsar MCP Server

Pulsar MCP Server

by Germain-D
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pulsar_list_connectors

List all Apache Pulsar connectors of a specified type (source or sink) to view available connectors for data integration.

Instructions

List all connectors of specified type (source or sink)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pulsar_list_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault
connector_typeNoType of connectors to listsource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. The verb 'list' implies a read-only, non-destructive operation, which is appropriate for a listing tool. No behavioral traits beyond the stated action are needed.

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

Conciseness5/5

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

A single, concise sentence of 8 words that is front-loaded and contains no unnecessary information.

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 simplicity of the tool (1 param, no output schema), the description adequately covers what the tool does. It could optionally hint at the return format, but the agent can infer from the context and sibling tools.

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 the parameter intent is fully captured. The description adds no extra meaning beyond what the schema already provides ('Type of connectors to list' with enum values).

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 'List all connectors of specified type (source or sink)' clearly states the action (list), resource (connectors), and filter (type). It distinguishes from the sibling tool pulsar_all_connectors, which lists all connectors without type filtering.

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

Usage Guidelines3/5

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

The description implies usage when you want to list connectors of a specific type, but it does not explicitly mention when to use the alternative pulsar_all_connectors or provide any when-not guidance.

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