Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Subject Mode

get_subject_mode
Read-onlyIdempotent

Retrieves the operational mode for a specific Kafka Schema Registry subject so you can verify compatibility or read/write behavior before schema operations.

Instructions

Get the operational mode for a specific subject.

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

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.1/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 safety profile is covered. The description adds the backward-compatibility/deprecation context and a performance rationale, which is genuinely beyond the annotations, but it does not describe what a 'mode' is, what values it can take, or what happens for an unknown subject.

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 compact sentences, with the core action front-loaded before the deprecation note. Nothing is padded, though the note is slightly indirect ('consider using... instead') for an agent that needs a clear decision rule.

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, no schema descriptions, and no annotation detail on return shape, the description should explain what a mode value looks like and what the optional context/registry scoping means. For a three-parameter lookup in a multi-registry schema server, that information is missing.

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. The description only names 'subject'; the 'context' and 'registry' parameters, both defaulting to null, are left completely unexplained, including what the null default resolves to. It adds essentially no meaning beyond the parameter names.

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 the operational mode for a specific subject.' An agent understands it returns the mode value scoped to one subject. It does not explicitly distinguish itself from the sibling 'get_mode', so the differentiation is only partial.

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 routes callers to the 'subject://{name}/{context}/{subject}/mode' resource for better performance, which is useful steering, but it says nothing about when this tool is still preferable or how it differs from 'get_mode'. Usage is implied rather than spelled out.

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