Skip to main content
Glama
Sign In
ms-sentinel-mcp-server

ms-sentinel-mcp-server

by dstreefkerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

sentinel_analytics_rules_count_by_technique

Count Microsoft Sentinel analytics rules by MITRE ATT&CK technique to analyze security coverage and identify gaps in threat detection.

Instructions

Count Sentinel analytics rules by MITRE technique.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kwargs": "<kwargs>"
    },
    "name": "sentinel_analytics_rules_count_by_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwargsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior1/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 only states what the tool does ('Count...') without explaining how it behaves—e.g., whether it requires authentication, has rate limits, returns aggregated data, or handles errors. This is inadequate for a tool with no annotation coverage.

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 with no wasted words, clearly front-loading the core purpose. It is appropriately sized for a simple counting operation, though its 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.

Completeness2/5

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

Given the complexity (a counting operation with a parameter), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It fails to explain parameter usage, behavioral traits, or output format, making it insufficient for an agent to use the tool effectively without additional context.

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 one required parameter ('kwargs') with 0% description coverage, and the tool description provides no information about parameters. It does not explain what 'kwargs' should contain (e.g., filter criteria, MITRE technique IDs) or its format, leaving the parameter completely 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 verb ('Count') and resource ('Sentinel analytics rules') with a specific grouping criterion ('by MITRE technique'), making the purpose unambiguous. It distinguishes from some siblings like 'sentinel_analytics_rule_list' (which lists rules) but not explicitly from 'sentinel_analytics_rules_count_by_tactic' (which counts by tactic instead of technique).

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 provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'sentinel_analytics_rules_count_by_tactic' for counting by tactic or 'sentinel_analytics_rule_list' for listing rules, leaving the agent to infer usage context based on the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools