Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Test All Registries

test_all_registries
Read-onlyIdempotent

Tests connections to all configured Kafka Schema Registries so you can verify access before performing schema operations.

Instructions

Test connections to all configured registries.

NOTE: This tool is maintained for backward compatibility. Consider using the 'registry://status' 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_all_registries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.0.0

TDQS

A3.8/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 without the description. The description adds deprecation status and the performance motivation for the successor, but says nothing about what a 'test' actually does — network probes, latency, partial failures — which matters for a connection-testing tool.

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?

Two short statements: purpose front-loaded, deprecation note second, zero filler. The NOTE prefix is slightly verbose but earns its emphasis for a deprecated tool.

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?

For a no-param, no-output-schema read-only tool, the definition covers purpose, deprecation, and preferred alternative — enough to call it correctly. The only omission is any hint of what a test result contains or how long it may take.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is nothing to disambiguate; the description correctly implies the all-registries scope is fixed with no filtering options. Baseline 4 applies for a no-parameter tool.

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?

The first sentence gives a specific verb and resource ('Test connections to all configured registries'), clearly scoped to the 'all' case. It stops short of distinguishing itself from the sibling test_registry_connection, which an agent could reasonably confuse it with.

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?

It explicitly flags itself as backward-compatibility-only and names a preferred alternative ('registry://status' resource) for better performance, which is strong routing guidance. It doesn't state when this tool is still the correct choice over test_registry_connection, leaving one gap.

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