Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Subject Config

get_subject_config
Read-onlyIdempotent

Retrieves configuration settings for a specific Kafka Schema Registry subject so you can inspect its schema compatibility configuration.

Instructions

Get configuration settings for a specific subject.

NOTE: This tool is maintained for backward compatibility. Consider using the 'subject://{name}/{context}/{subject}/config' resource instead for better performance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subject": "<subject>"
    },
    "name": "get_subject_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
subjectYes
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • removedInput schema / properties / subject / title
      Removed value: -"Subject"
  2. First observedv1.0.0

TDQS

B3.3/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 safety and repeatability are covered. The description adds genuine value beyond that by disclosing deprecation status and a performance rationale for the resource alternative, but it never says what the returned configuration contains or whether it resolves defaults.

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 sentences, front-loaded with the core purpose and followed by the deprecation note. Nothing is padded or redundant; the only mild inefficiency is that the note is more prominent than the actual behavior of the call.

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?

There is no output schema, no annotation detail on return shape, and 0% parameter documentation, so the description should explain what configuration is returned and what the optional scoping parameters do. It covers the deprecation angle well but leaves the mechanics of calling the tool under-specified for a three-parameter tool.

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% across three parameters, so the description carries the full burden and fails to meet it. Only 'subject' is implicitly referenced; 'context' and 'registry' are never explained, so an agent cannot tell whether they are filters, scoping selectors, or defaults. The resource template in the note hints at name/context/subject ordering, which is the only partial compensation.

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 configuration settings for a specific subject. That distinguishes it from get_global_config by scope, though the description never explicitly contrasts the two, leaving the subject-vs-global distinction implicit.

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?

Explicitly tells the agent this tool exists only for backward compatibility and points to the 'subject://{name}/{context}/{subject}/config' resource as the preferred path for better performance. That is concrete when-to-use guidance for one alternative, but it says nothing about when to prefer this over sibling tools like get_subject_mode when both touch subject-level state.

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