Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Test Registry Connection

test_registry_connection
Read-onlyIdempotent

Verify connectivity to a specified Kafka Schema Registry, confirming the endpoint is reachable before schema operations.

Instructions

Test connection to a specific registry.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://status/{name}' resource instead for better performance.

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": "test_registry_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / registry / title
      Removed value: -"Registry"
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds genuinely useful lifecycle context (kept only for backward compatibility, slower than the resource alternative), but never says what a "test" actually verifies or what a failure looks like.

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?

One-line purpose followed by a clearly separated NOTE, front-loaded and free of filler. The deprecation note is placed after the purpose, which is the right order.

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

Completeness3/5

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

There is no output schema, so the description should say what the test returns (pass/fail, latency, error detail) and what the null-registry default means; it covers neither. Given a one-parameter, single-purpose tool the gaps are modest but real.

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

Parameters2/5

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

The single `registry` parameter has 0% schema description coverage and is optional with a null default, yet the description says nothing about it — notably not what happens when it is omitted (does it fall back to a default registry?). The phrase "a specific registry" hints at intent but adds no usable parameter meaning.

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

Purpose4/5

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

Names a specific verb and resource ("Test connection to a specific registry"), and the word "specific" implicitly contrasts with the sibling test_all_registries. It stops short of naming that sibling explicitly, so the differentiation is by inference rather than statement.

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?

Gives explicit steering: the tool is backward-compatibility only, and the 'registry://status/{name}' resource is named as the preferred alternative for better performance. It does not address when to prefer test_registries / test_all_registries among the tool siblings, but the alternative it does name is concrete and actionable.

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