Skip to main content
Glama
dstreefkerk

ms-sentinel-mcp-server

by dstreefkerk

sentinel_connectors_list

Retrieve a list of data connectors to monitor and manage security data sources in Microsoft Sentinel.

Instructions

List data connectors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kwargsYes

Implementation Reference

  • The SentinelConnectorsListTool class provides the core implementation of the 'sentinel_connectors_list' tool, including metadata (name, description) and the 'run' method that fetches and formats the list of Sentinel data connectors using the Azure SecurityInsights API.
    class SentinelConnectorsListTool(MCPToolBase):
        """
        MCP tool for listing Sentinel data connectors.
    
        This tool supports both MCP server context (using ctx.request_context) and
        direct invocation for integration tests.
        If ctx.request_context is not present, Azure credentials and context are
        loaded from environment variables, as required by project architecture guidelines.
        """
    
        name = "sentinel_connectors_list"
        description = "List data connectors"
    
        async def run(self, ctx: Context, **kwargs):
            """List available Sentinel data connectors in the workspace.
    
            Args:
                ctx (Context): The MCP server or test context.
                **kwargs: Additional keyword arguments (unused).
            Returns:
                dict: Result containing connector list or error information.
            """
            logger = self.logger
            workspace_name, resource_group, subscription_id = self.get_azure_context(ctx)
            if not (workspace_name and resource_group and subscription_id):
                logger.error("Missing Azure context for listing data connectors.")
                return {"error": "Missing Azure context for listing data connectors."}
            try:
                client = self.get_securityinsight_client(subscription_id)
                connectors = client.data_connectors.list(
                    resource_group_name=resource_group,
                    workspace_name=workspace_name,
                )
                connector_list = list(connectors)
                result = []
                for c in connector_list:
                    connector_type = getattr(c, "kind", "Unknown")
                    result.append(
                        {
                            "name": getattr(c, "name", None),
                            "kind": connector_type,
                            "id": getattr(c, "id", None),
                            "etag": getattr(c, "etag", None),
                            "type": getattr(c, "type", None),
                        }
                    )
                return {
                    "count": len(result),
                    "connectors": result,
                    "note": (
                        "⚠️ Connector list may be incomplete. Built-in and gallery-deployed "
                        "connectors are not included due to Azure API limitations. "
                        "Manual verification recommended."
                    ),
                }
            except Exception as e:
                logger.error("Error listing data connectors: %s", e)
                return {"error": "Error listing data connectors: %s" % str(e)}
  • The 'register_tools' function registers the SentinelConnectorsListTool (sentinel_connectors_list) with the MCP server instance.
    def register_tools(mcp):
        """Register all data connector tools with the MCP server.
    
        Args:
            mcp: The MCP server instance.
        """
        SentinelConnectorsListTool.register(mcp)
        SentinelConnectorsGetTool.register(mcp)
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action without any details on permissions required, rate limits, pagination, or what the output looks like (e.g., list format, error handling). This is inadequate for a tool with potential security or operational implications.

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 extremely concise with a single phrase 'List data connectors', which is front-loaded and wastes no words. It efficiently communicates the core action, though this brevity contributes to gaps in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity implied by the sibling tools (e.g., security operations), no annotations, no output schema, and 0% parameter coverage, the description is severely incomplete. It fails to address critical aspects like authentication needs, data format, or error conditions, making it insufficient for safe and effective use.

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

Parameters1/5

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

The input schema has 1 parameter (kwargs) with 0% description coverage, and the tool description provides no information about parameters. It doesn't explain what 'kwargs' represents (e.g., filtering options, configuration) or how to use it, leaving the parameter completely undocumented.

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 'List data connectors' clearly states the action (list) and resource (data connectors), providing basic purpose. However, it lacks specificity about what data connectors are in this context (e.g., Sentinel security connectors) and doesn't distinguish from sibling tools like sentinel_connectors_get, which suggests a similar domain but different operation.

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. For example, it doesn't clarify if this is for browsing all connectors versus filtered searches, or how it relates to sentinel_connectors_get. The description offers no context on 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

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/dstreefkerk/ms-sentinel-mcp-server'

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