Skip to main content
Glama
Sign In
MCP Kafka Schema Reg

MCP Kafka Schema Reg

by aywengo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Export Global

export_global
Read-onlyIdempotent

Exports all contexts and schemas from a Kafka Schema Registry, with options to include configuration, metadata, and version details.

Instructions

Export all contexts and schemas from a registry.

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

Input Schema

NameRequiredDescriptionDefault
registryNo
include_configNo
include_metadataNo
include_versionsNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0
  2. Removedv2.2.2
  3. 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. Beyond that the description adds nothing: it does not say what an 'export' produces (file, payload, archive), whether large registries are truncated, or how the optional inclusion flags change the result.

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, which is structurally sound. Its brevity, however, comes at the cost of the omissions captured in the other dimensions rather than reflecting deliberate economy.

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 four-parameter bulk-export tool with no output schema and no parameter documentation, the definition is too thin. An agent cannot tell what it will receive back or what the inclusion flags do, which is exactly the information the description should supply.

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% for four parameters, so the description must carry the burden and does not. Only 'from a registry' loosely gestures at the registry parameter; include_config, include_metadata, and include_versions (default 'all') are never explained, even though they materially change what is exported.

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: exporting all contexts and schemas from a registry. The word 'all' distinguishes it in scope from siblings like export_context and export_schema, though it never names them explicitly.

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?

There is no when-to-use guidance and no mention of the obvious alternative export_global_interactive or when a bulk export is preferable to per-context/per-schema exports. Usage is only implied by the word 'all'.

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

Deploy Server

Other Tools