Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Get Schema Versions

get_schema_versions
Read-onlyIdempotent

Retrieve all versions of a schema for a given subject from Kafka Schema Registry to inspect version history or compare schema changes.

Instructions

Get all versions of a schema for a subject.

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

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

A3.5/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 backward-compatibility and performance context, but does not explain return ordering, pagination, or what version metadata is included.

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?

The description is two short sentences, front-loads the core action, and immediately follows with the backward-compatibility note. There is no unnecessary wording.

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 versions lookup, the description covers the main purpose and alternative resource path. However, with no output schema and zero parameter description coverage, it should do more to explain context/registry semantics and what the returned versions look like.

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%, so the description must compensate for three undocumented parameters. It only implies that subject identifies the schema subject and gives no meaning for context or registry, leaving important invocation details unclear.

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 all versions of a schema for a subject. It is clear enough to distinguish from count_schema_versions and get_schema, though it does not explicitly compare itself to those siblings.

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 clearly says the tool is maintained for backward compatibility and recommends the schema resource for better performance. That gives useful when-to-use guidance, but it does not say when to prefer this tool over sibling tools such as count_schema_versions or get_schema.

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