Skip to main content
Glama
aywengo

MCP Kafka Schema Reg

get_operation_info_tool

Retrieve detailed metadata and information about specific operations in the MCP Kafka Schema Registry server. Input the operation name to access relevant data and insights.

Instructions

Get detailed information about MCP operations and their metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_nameNo

Implementation Reference

  • Handler function that retrieves and formats operation metadata including duration, async pattern, guidance, and registry mode.
    def get_operation_info(operation_name: str, registry_mode: str) -> Dict[str, Any]:
        """Get operation metadata for MCP client guidance."""
        metadata = OPERATION_METADATA.get(
            operation_name,
            {"duration": OperationDuration.QUICK, "pattern": AsyncPattern.DIRECT},
        )
        return {
            "operation": operation_name,
            "expected_duration": metadata["duration"].value,
            "async_pattern": metadata["pattern"].value,
            "guidance": _get_operation_guidance(metadata),
            "registry_mode": registry_mode,
        }
  • Output JSON schema for the get_operation_info_tool, allowing arbitrary object properties.
    "get_operation_info_tool": {"type": "object", "additionalProperties": True},
  • Static metadata dictionary defining operation characteristics used by the handler.
            "pattern": AsyncPattern.DIRECT,
        },
        "count_schemas": {
            "duration": OperationDuration.MEDIUM,
            "pattern": AsyncPattern.TASK_QUEUE,
        },
        "count_schema_versions": {
            "duration": OperationDuration.QUICK,
            "pattern": AsyncPattern.DIRECT,
        },
        "get_registry_statistics": {
            "duration": OperationDuration.LONG,
            "pattern": AsyncPattern.TASK_QUEUE,
        },
    }
  • Helper function to generate user guidance based on operation metadata.
    def _get_operation_guidance(metadata: Dict[str, Any]) -> str:
        """Generate guidance text for operation."""
        if metadata["pattern"] == AsyncPattern.TASK_QUEUE:
            return "Long-running operation. Returns task_id immediately. Use get_task_status() to monitor progress."
        else:
            return "Quick operation. Returns results directly."
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 retrieving 'detailed information' but does not specify what that entails (e.g., format, scope, or limitations), nor does it address permissions, rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior.

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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 tool's complexity (information retrieval with one parameter), lack of annotations, 0% schema description coverage, and no output schema, the description is insufficient. It does not explain what 'detailed information' includes, how to use the parameter, or what the return values are, making it incomplete for effective use.

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?

The input schema has one parameter ('operation_name') with 0% description coverage, and the tool description does not mention parameters at all. This fails to compensate for the lack of schema documentation, leaving the parameter's purpose and usage unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Get[s] detailed information about MCP operations and their metadata,' which provides a clear verb ('Get') and resource ('MCP operations and their metadata'). However, it does not distinguish this from sibling tools like 'get_mcp_compliance_status_tool' or 'get_registry_info,' which also retrieve information, making the purpose somewhat vague in context.

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 offers no guidance on when to use this tool versus alternatives. With many sibling tools that retrieve information (e.g., 'get_mcp_compliance_status_tool,' 'get_registry_info'), there is no indication of specific contexts, prerequisites, or exclusions for this tool's use.

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