Skip to main content
Glama
Sign In
MCP Kafka Schema Reg

MCP Kafka Schema Reg

by aywengo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Export Context

export_context
Read-onlyIdempotent

Exports all schema subjects in a specified Kafka Schema Registry context, with options to include config, metadata, and versions for backup or migration.

Instructions

Export all subjects within a context.

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": {
      "context": "<context>"
    },
    "name": "export_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYes
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 and idempotentHint, so safety is covered elsewhere. The description adds no behavioral context about what an export produces, how large it may be, whether defaults cause config/metadata/version data to be included, or what the response looks like — all relevant for an export that can silently widen or narrow its payload.

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?

One short sentence with no filler, which is structurally clean and front-loaded. However, the brevity is under-specification rather than economy given five undocumented parameters, so it does not earn a high score.

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 five-parameter export tool with no output schema and no annotation-derived detail about results, the definition leaves the agent guessing about scope flags and return shape. It is not wrong, but it is far from sufficient to invoke confidently.

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 five parameters, so the description carries the full burden and fails. It only implicitly touches 'context' and says nothing about registry, include_config, include_metadata, or include_versions — parameters whose defaults (true, true, 'all') materially change the export contents.

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 subjects') scoped to a context, which is enough to distinguish it from export_global and export_subject in spirit. It never names those siblings or clarifies the boundary explicitly, so it stops short of a 5.

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, no statement of when to pick this over export_global, export_subject, or export_schema, and no prerequisites or preconditions mentioned. The agent must infer selection purely from the tool name and the word 'context'.

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