Skip to main content
Glama
Sign In
azure-query-mcp

azure-query-mcp

by kapetanios55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_incidents

Read-onlyIdempotent

Identify Microsoft Sentinel incidents by listing them from the SecurityIncident table. Filter results by severity, status, or time range to prioritize security triage.

Instructions

List Microsoft Sentinel incidents (latest state of each) from the SecurityIncident table, newest first. Use to find incidents to triage; then call get_incident for details.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "list_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusesNoFilter by status.
timespanNoISO 8601 duration back from now (P7D, PT12H), or an interval: start/end (2026-10-01T00:00:00Z/2026-10-02T00:00:00Z) or start/duration (2026-10-01T08:00:00Z/PT6H). Times need Z or an offset. Default P7D.P7D
maxResultsNoMaximum incidents returned.
severitiesNoFilter by severity.
workspaceIdYesWorkspace ID (GUID) or the workspace's full ARM resource ID; list_workspaces returns both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: it returns the *latest* state of each incident (i.e., deduplicated across the update-history rows in SecurityIncident) and orders results newest first. It omits what happens when results are truncated at maxResults, which is the remaining behavioral gap.

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?

Two sentences, zero filler. The identifying scope ('latest state of each', 'newest first') is front-loaded, and the routing hint follows immediately.

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

Completeness4/5

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

For a filtered list tool with full schema coverage and a pointer to get_incident for detail, an agent has what it needs to call correctly. The absence of an output schema leaves the returned incident fields (id, title, severity, status) unspecified, and truncation/pagination behavior is unstated — minor but real gaps.

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

Parameters3/5

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

Schema description coverage is 100% — statuses, severities, timespan formats, maxResults bounds and workspaceId format are all documented in the schema itself. The description adds nothing parameter-specific ('newest first' is ordering behavior, not a parameter). Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb (List) and resource (Microsoft Sentinel incidents), plus non-obvious scope details: 'latest state of each' and 'from the SecurityIncident table, newest first'. This distinguishes it cleanly from get_incident and from generic query siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use to find incidents to triage; then call get_incident for details.' That gives a clear entry-point workflow with a named alternative. It does not say when NOT to use it (e.g., when custom KQL via query_workspace is preferable), so it stops short of full when/when-not coverage.

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