Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Registry Info

get_registry_info
Read-onlyIdempotent

Retrieve detailed information about a specific Kafka Schema Registry to inspect its configuration, compatibility settings, and metadata.

Instructions

Get detailed information about a specific registry.

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

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description isn't required to establish safety. It does add genuine extra context — that the tool is maintained for backward compatibility and is slower than the resource equivalent — but omits what happens when the registry parameter is omitted and what is returned.

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 core purpose is front-loaded in one sentence and the deprecation note is clearly separated, so it scans quickly. The 'NOTE:' is slightly verbose for two lines but nothing is truly wasted.

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?

For a one-parameter read-only lookup with no output schema and existing annotations, the description is nearly sufficient, but the null-default registry behavior and the shape of the returned 'detailed information' are left unexplained. Those are the two things an agent would most likely guess wrong.

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?

Schema description coverage is 0% and the single parameter is optional with default null, yet the description never explains it: no format for the registry name (short name vs hostname vs URL) and no statement of which registry is used when it is null. The description's 'specific registry' phrasing actually implies the parameter is required, which conflicts with required=0.

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 concrete verb+resource: 'Get detailed information about a specific registry,' which is clear and distinguishable from siblings like get_registry_statistics or test_registry_connection. It stops short of stating what 'detailed information' actually contains (config, scopes, URL?), so the scope of the return is uncertain.

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 NOTE does route the agent away from this tool toward an alternative ('registry://info/{name}' resource), which is real usage guidance. However, it frames the choice only as performance/backward-compatibility rather than stating a condition under which this tool is still the correct call, and it gives no guidance relative to the listed sibling tools.

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