Skip to main content
Glama
dstreefkerk

ms-sentinel-mcp-server

by dstreefkerk

sentinel_connectors_get

Retrieve a specific Azure Sentinel data connector by its ID to access configuration details and monitoring settings.

Instructions

Get a specific data connector by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kwargsYes

Implementation Reference

  • The async run method implements the core execution logic for the sentinel_connectors_get tool: validates Azure context and data_connector_id input, retrieves the specific data connector using Azure Security Insights client, and returns its details or error.
    async def run(self, ctx: Context, **kwargs):
        """Retrieve a specific Sentinel data connector by its ID.
    
        Args:
            ctx (Context): The MCP server or test context.
            **kwargs: Keyword arguments containing 'data_connector_id'.
        Returns:
            dict: Connector details 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 getting data connector.")
            return {"error": "Missing Azure context for getting data connector."}
        data_connector_id = self._extract_param(kwargs, "data_connector_id")
        if not data_connector_id:
            logger.error("Missing required parameter: data_connector_id")
            return {"error": "Missing required parameter: data_connector_id"}
        try:
            client = self.get_securityinsight_client(subscription_id)
            connector = client.data_connectors.get(
                resource_group_name=resource_group,
                workspace_name=workspace_name,
                data_connector_id=data_connector_id,
            )
            return {
                "name": getattr(connector, "name", None),
                "type": getattr(connector, "type", None),
                "kind": getattr(connector, "kind", None),
                "id": getattr(connector, "id", None),
                "etag": getattr(connector, "etag", None),
                "properties": getattr(connector, "properties", None),
            }
        except Exception as e:
            logger.error("Error getting data connector: %s", e)
            return {"error": "Error getting data connector: %s" % str(e)}
  • Tool class declaration, name, description, and docstring defining the input requirement (data_connector_id in kwargs) and purpose.
    class SentinelConnectorsGetTool(MCPToolBase):
        """
        MCP tool for retrieving a specific Sentinel data connector by ID.
    
        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_get"
        description = "Get a specific data connector by ID"
  • Registers the SentinelConnectorsGetTool instance with the MCP server via the register_tools function.
    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. It states 'Get' which implies a read operation, but doesn't disclose any behavioral traits such as authentication needs, rate limits, error handling, or what the response looks like. This leaves significant gaps for an agent.

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's 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.

Completeness1/5

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

Given the complexity of a security tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, behavior, output format, and differentiation from siblings, making it inadequate for effective tool 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 description doesn't add any meaning beyond the tool name. It doesn't explain what 'kwargs' should contain (e.g., the connector ID format or other details), leaving the parameter undocumented.

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 action ('Get') and resource ('a specific data connector by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'sentinel_connectors_list' or explain what a 'data connector' is in this 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?

No guidance is provided on when to use this tool versus alternatives like 'sentinel_connectors_list' for listing connectors or other get tools for different resources. The description implies usage when you have a specific connector ID, but offers no explicit context 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