Skip to main content
Glama
aywengo

MCP Kafka Schema Reg

describe_workflow

Retrieve detailed information about a workflow definition in Kafka Schema Registry. The tool accepts a workflow_id as input to provide specific workflow details for better management and understanding.

Instructions

Get detailed information about a workflow definition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'describe_workflow' tool. It fetches the workflow definition using get_workflow_by_id, constructs a detailed step graph with field information, and returns a comprehensive JSON description of the workflow structure.
    @self.mcp.tool(description="Get detailed information about a workflow definition")
    async def describe_workflow(workflow_id: str) -> str:
        """Get detailed workflow information."""
        workflow = get_workflow_by_id(workflow_id)
    
        if not workflow:
            return json.dumps({"error": f"Workflow '{workflow_id}' not found"})
    
        # Build step graph
        step_graph = {}
        for step_id, step in workflow.steps.items():
            step_info = {
                "id": step.id,
                "title": step.title,
                "description": step.description,
                "type": step.elicitation_type.value,
                "fields": [
                    {
                        "name": field.name,
                        "type": field.type,
                        "description": field.description,
                        "required": field.required,
                        "options": field.options if field.type == "choice" else None,
                    }
                    for field in step.fields
                ],
                "next_steps": step.next_steps,
            }
            step_graph[step_id] = step_info
    
        return json.dumps(
            {
                "workflow_id": workflow.id,
                "name": workflow.name,
                "description": workflow.description,
                "initial_step_id": workflow.initial_step_id,
                "total_steps": len(workflow.steps),
                "steps": step_graph,
                "metadata": workflow.metadata,
            }
        )
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. It states 'Get detailed information', which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'detailed information' entails beyond the output schema.

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 a single, efficient sentence that is front-loaded with the core action and resource. There is no wasted verbiage, making it highly concise and well-structured.

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?

Given the tool's low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete parameter guidance, it lacks depth for a tool that might involve workflow-specific nuances, leaving gaps in overall context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and 1 parameter, the description doesn't add specific meaning to the 'workflow_id' parameter. However, the baseline is 4 for 0 parameters, and since there's only one parameter, the lack of additional semantics is less critical, but it doesn't 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?

The description clearly states the verb 'Get' and resource 'workflow definition' with specificity 'detailed information', making the purpose evident. However, it doesn't distinguish this from potential siblings like 'get_workflow_status' or 'list_workflows', which could provide overlapping information about workflows.

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 guidance is provided on when to use this tool versus alternatives such as 'get_workflow_status' or 'list_workflows'. The description implies usage for retrieving details but lacks explicit context, prerequisites, or exclusions.

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