Skip to main content
Glama
aywengo

MCP Kafka Schema Reg

bulk_schema_update

Update multiple Kafka schemas in bulk with interactive guidance, pattern matching, and support for compatibility settings, naming conventions, and metadata updates. Use dry runs for testing.

Instructions

Update schemas in bulk with interactive guidance.

Supports compatibility settings, naming conventions, and metadata updates. Pattern matching supported (e.g., test-, deprecated-).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_sizeNo
dry_runNo
patternNo
update_typeNocompatibility

Implementation Reference

  • Core handler implementation for bulk_schema_update tool. Orchestrates schema selection, update type elicitation, parameter gathering, preview generation, user confirmation, and operation execution.
    async def _handle_bulk_schema_update(self) -> Dict[str, Any]:
        """Handle bulk schema update operations"""
        # Step 1: Select schemas
        schemas = await self._elicit_schema_selection("Select schemas to update", allow_patterns=True)
    
        # Step 2: Select update type
        update_type = await self._elicit_update_type()
    
        # Step 3: Get update parameters
        update_params = await self._elicit_update_parameters(update_type)
    
        # Step 4: Preview changes
        preview = await self._generate_preview(BulkOperationType.SCHEMA_UPDATE, schemas, update_params)
    
        # Step 5: Confirm operation
        if not await self._confirm_operation(preview):
            return {"status": "cancelled", "reason": "User cancelled operation"}
    
        # Step 6: Execute operation
        return await self._execute_bulk_operation(BulkOperationType.SCHEMA_UPDATE, schemas, update_params, preview)
  • MCP tool registration for 'bulk_schema_update', including name, description, and input schema definition.
    tools.append(
        Tool(
            name="bulk_schema_update",
            description=(
                "Update schemas in bulk with interactive guidance. "
                "Supports compatibility settings, naming conventions, and metadata updates. "
                "Pattern matching supported (e.g., test-*, deprecated-*)."
            ),
            inputSchema={
                "type": "object",
                "properties": {
                    "pattern": {"type": "string", "description": "Schema name pattern (e.g., 'test-*', 'prod-*')"},
                    "update_type": {
                        "type": "string",
                        "enum": ["compatibility", "naming", "metadata"],
                        "description": "Type of update to perform",
                    },
                    "dry_run": {"type": "boolean", "default": True, "description": "Preview changes without applying"},
                    "batch_size": {
                        "type": "integer",
                        "default": 10,
                        "description": "Number of schemas to process at once",
                    },
                },
                "required": ["update_type"],
            },
        )
    )
  • Internal registration of the schema update handler within the BulkOperationsWizard class.
    def _register_handlers(self) -> Dict[BulkOperationType, Callable]:
        """Register operation handlers"""
        return {
            BulkOperationType.SCHEMA_UPDATE: self._handle_bulk_schema_update,
            BulkOperationType.MIGRATION: self._handle_bulk_migration,
            BulkOperationType.CLEANUP: self._handle_bulk_cleanup,
            BulkOperationType.CONFIGURATION: self._handle_bulk_configuration,
        }
  • Tool dispatcher that handles the 'bulk_schema_update' tool call by invoking the wizard's start_wizard with SCHEMA_UPDATE type.
    elif tool_name == "bulk_schema_update":
        # Direct schema update with parameters
        # In real implementation, would pass parameters to wizard
        return await wizard.start_wizard(BulkOperationType.SCHEMA_UPDATE)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'interactive guidance' and 'Supports compatibility settings, naming conventions, and metadata updates', which gives some context about what the tool does. However, it lacks critical behavioral details such as whether this is a read-only or destructive operation, permission requirements, rate limits, or what 'interactive guidance' entails. For a bulk update tool with no annotation coverage, this is insufficient.

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?

The description is concise and well-structured with three sentences. The first sentence states the core purpose, and the subsequent sentences list key features. There is no unnecessary information, and it is front-loaded with the main action. A minor deduction for not being maximally efficient, as it could integrate features more tightly, but overall it's clear and to the point.

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?

Given the complexity of a bulk update tool with 4 parameters, 0% schema description coverage, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., destructiveness, permissions), parameter meanings, expected outputs, and error handling. The mention of 'interactive guidance' and features provides some context, but it's insufficient for safe and effective use by an AI agent.

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%, meaning none of the 4 parameters (batch_size, dry_run, pattern, update_type) have descriptions in the schema. The description mentions 'Pattern matching supported (e.g., test-*, deprecated-*)', which loosely relates to the 'pattern' parameter, and 'compatibility settings' might relate to 'update_type'. However, it doesn't explain what 'batch_size', 'dry_run', or 'update_type' mean, their valid values, or how they interact. The description adds minimal semantic value beyond the schema.

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 clearly states the tool's purpose: 'Update schemas in bulk with interactive guidance.' It specifies the verb ('Update'), resource ('schemas'), and scope ('in bulk'), and mentions interactive guidance. However, it doesn't explicitly differentiate from sibling tools like 'bulk_schema_cleanup' or 'bulk_schema_migration', which prevents a score of 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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Supports compatibility settings, naming conventions, and metadata updates' and 'Pattern matching supported', but these are features, not usage instructions. There is no mention of prerequisites, when-not-to-use scenarios, or comparisons to sibling tools like 'bulk_schema_cleanup' or 'bulk_schema_migration'.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aywengo/kafka-schema-reg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server