Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Global Config

get_global_config
Read-onlyIdempotent

Retrieves global Kafka Schema Registry configuration settings, optionally scoped by context or registry, for backward-compatible config access.

Instructions

Get global configuration settings.

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

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

B3.1/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 useful lifecycle context (deprecated in favor of a resource, performance rationale) but discloses nothing about what the returned config contains or how it is scoped.

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 lines, purpose front-loaded, deprecation note clearly separated and labeled. No filler; the only gap is that the brevity comes at the cost of parameter and scoping detail rather than being offset elsewhere.

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?

A two-parameter tool with 0% schema coverage and no output schema leaves the description as the only explanatory source, and it explains neither the parameters nor the shape/scope of the returned configuration. The deprecation pointer is helpful but does not fill that gap.

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 description never mentions the two parameters 'context' and 'registry' at all, so an agent has no idea whether omitting them yields all contexts, the default registry, or an error. With zero schema coverage the description had to compensate and does not.

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?

States a specific verb and resource: 'Get global configuration settings.' An agent can tell this returns global-scope config, but nothing distinguishes it from siblings such as get_subject_config, get_mode, or get_default_registry, so the scope boundary between 'global' and 'subject'/'registry' config is left to inference.

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 gives one real routing signal: prefer the 'registry://{name}/config' resource for better performance, and this tool is kept for backward compatibility. That is a genuine alternative plus a reason, but it says nothing about when to use this tool over sibling config tools, nor whether it is only for legacy clients.

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