Skip to main content
Glama
dstreefkerk

ms-sentinel-mcp-server

by dstreefkerk

sentinel_ml_analytics_settings_list

List all machine learning analytics settings in your Microsoft Sentinel workspace to configure and manage security monitoring rules.

Instructions

List all Sentinel ML analytics settings in the current workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kwargsYes

Implementation Reference

  • The async run method of SentinelMLAnalyticsSettingsListTool that implements the core tool logic. It fetches Azure context, lists ML analytics settings via the security_ml_analytics_settings.list API, extracts key fields (id, name, description, enabled), and returns a structured result with validation and error handling.
    async def run(self, ctx: Context, **kwargs):
        """
        List all ML analytics settings in the current Sentinel workspace.
        Returns MCP-compliant dict with 'settings', 'valid', 'errors', and 'error'.
        """
        logger = self.logger
        result = {"settings": [], "valid": False, "errors": []}
        workspace_name, resource_group, subscription_id = self.get_azure_context(ctx)
        if not (workspace_name and resource_group and subscription_id):
            error_msg = (
                "Missing required Azure context (workspace_name, resource_group, "
                "subscription_id)."
            )
            logger.error(error_msg)
            result["error"] = error_msg
            result["errors"].append(error_msg)
            return result
        try:
            client = self.get_securityinsight_client(subscription_id)
            # Use the preview API version for ML Analytics support
            ml_settings_paged = client.security_ml_analytics_settings.list(
                resource_group, workspace_name
            )
            settings = []
            for s in ml_settings_paged:
                s_dict = s.as_dict() if hasattr(s, "as_dict") else dict(s)
                settings.append(
                    {
                        "id": s_dict.get("id"),
                        "name": s_dict.get("name"),
                        "description": s_dict.get("description"),
                        "enabled": s_dict.get("enabled"),
                    }
                )
            result["settings"] = settings
            result["valid"] = True
        except Exception as ex:
            error_msg = f"Error listing ML analytics settings: {ex}"
            logger.exception(error_msg)
            result["error"] = error_msg
            result["errors"].append(error_msg)
        return result
  • Registers the SentinelMLAnalyticsSettingsListTool class with the MCP server instance inside the register_tools function.
    SentinelMLAnalyticsSettingsListTool.register(mcp)
  • Tool name and description definition, used by MCPToolBase for tool schema, input/output expectations, and registration.
    name = "sentinel_ml_analytics_settings_list"
    description = "List all Sentinel ML analytics settings in the current workspace."
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 it's a list operation, implying read-only behavior, but doesn't disclose details like pagination, rate limits, authentication requirements, or what 'all' entails (e.g., completeness, ordering). For a tool with no annotations, this leaves significant behavioral gaps.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly. Every part of the sentence adds value without redundancy.

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 no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It covers the basic purpose but lacks parameter details, behavioral context, and output information. For a tool with one parameter and no structured support, more guidance is needed to be fully helpful.

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. The description doesn't explain what 'kwargs' represents, its format, or how it affects the listing. With low schema coverage, the description fails to compensate, leaving parameters 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 ('List all') and resource ('Sentinel ML analytics settings'), with scope ('in the current workspace'). It distinguishes from sibling 'sentinel_ml_analytics_setting_get' by indicating it lists all settings rather than retrieving a single one. However, it doesn't explicitly differentiate from other list tools like 'sentinel_analytics_rule_list' beyond the resource type.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, when not to use it, or compare it to other list tools for similar resources (e.g., 'sentinel_analytics_rule_list'). Usage is implied by the resource name but not explicitly stated.

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