Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Mode

get_mode
Read-onlyIdempotent

Retrieves the current Schema Registry mode to verify whether a Kafka registry is operating in its expected configuration state.

Instructions

Get the current mode of the Schema Registry.

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

Input Schema

NameRequiredDescriptionDefault
contextNo
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/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 new context: deprecation status and a faster alternative resource. It does not describe what the returned mode values are (e.g., read-write vs. read-only vs. import) or whether defaults apply per registry.

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?

Two short sentences, no filler. The core action is stated first, and the deprecation note follows immediately, so an agent can stop reading once it has what it needs.

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 simple read-only getter with no output schema, the description is adequate but incomplete: the two optional parameters are entirely undocumented, and the possible mode values returned are never characterized, leaving the agent to interpret results on its own.

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% for both parameters (context and registry), and the description says nothing about either. The agent must guess whether registry selects a named registry connection and what context scoping means for mode lookup.

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 description states a specific verb and resource: 'Get the current mode of the Schema Registry.' The qualifier 'of the Schema Registry' implicitly scopes it to registry-level mode rather than subject-level mode, which helps separate it from get_subject_mode, but the sibling is never named explicitly.

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 gives a clear when-not: this tool is kept only for backward compatibility and the 'registry://mode' resource is preferred for performance. What's missing is any guidance on choosing between this and get_subject_mode when the agent actually needs tool-based access.

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