Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Default Registry

get_default_registry
Read-onlyIdempotent

Retrieves the current default Kafka Schema Registry so you can confirm which registry instance the MCP server uses by default.

Instructions

Get the current default registry.

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_default_registry"
  }
}

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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered structurally and the bar for the description is lower. Still, the description adds nothing beyond that: no indication of what is resolved (name vs. connection config), what happens when no default is set, or whether it is a cheap local lookup or a remote call.

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?

A single short sentence, front-loaded and free of filler, so there is no wasted wording. It is arguably under-specified rather than bloated, which is penalized under other dimensions rather than here.

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?

With no output schema, the description is the only place an agent could learn what 'the default registry' looks like as a return value, and it says nothing. For a zero-parameter lookup that is easy to call correctly, the missing piece is comprehension of the result and of the notion of 'default', which is exactly what an agent needs before calling.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The input schema fully closes the object with additionalProperties: false, leaving nothing for the description to compensate for.

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

Purpose3/5

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

The description names a specific verb and resource ('Get the ... registry'), but 'default registry' is not defined anywhere, and sibling tools like get_registry_info and get_global_config make it unclear whether this returns an identifier, a configuration object, or a registry record. The title merely restates the name, adding no distinguishing detail.

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?

There is no when-to-use or when-not-to-use guidance. An agent cannot tell from this sentence why it would call get_default_registry instead of get_registry_info or get_global_config, nor whether a default registry must exist first.

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