Skip to main content
Glama
MCP Kafka Schema Reg

MCP Kafka Schema Reg

Export Subject

export_subject
Read-onlyIdempotent

Exports all versions of a Kafka Schema Registry subject, with optional configuration, metadata, and version filtering for backup, comparison, or migration.

Instructions

Export all versions of a subject.

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": "export_subject"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
subjectYes
registryNo
include_configNo
include_metadataNo
include_versionsNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.2.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context / title
      Removed value: -"Context"
    • removedInput schema / properties / include_config / title
      Removed value: -"Include Config"
    • removedInput schema / properties / include_metadata / title
      Removed value: -"Include Metadata"
    • removedInput schema / properties / include_versions / title
      Removed value: -"Include Versions"
    • removedInput schema / properties / registry / title
      Removed value: -"Registry"
    • removedInput schema / properties / subject / title
      Removed value: -"Subject"
  2. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/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 only the 'all versions' scope; it does not say what the export produces, where it goes, or how context/registry selection affects output. 'All versions' also slightly conflicts with the include_versions parameter, whose default is 'all' but which accepts other values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but its brevity comes at the cost of substance rather than reflecting an efficient summary of a well-understood tool.

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?

For a 6-parameter tool with no output schema and no parameter documentation, one sentence is inadequate. An agent cannot determine what the returned artifact looks like or how the five optional parameters modify the export.

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 6 parameters, and the description only hints at the version dimension ('all versions'), leaving context, registry, include_config, include_metadata, and the range of include_versions values completely undocumented. The description does not compensate for the schema gap.

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: 'Export all versions of a subject.' This distinguishes it from the sibling export_* tools (export_context, export_global, export_schema) by scope, though the word 'export' leaves the destination/format of the export unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the many export_* and get_* siblings. The agent must infer that this is the tool for subject-scoped exports.

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