mcp-github-enterprise

List code-scanning alerts

list_code_scanning_alerts

Read-onlyIdempotent

List an organization's code-scanning alerts (CodeQL/SARIF) with rule, severity, state, and location; filter by alert state to review and triage security findings.

Instructions

List the organization's code-scanning (CodeQL/SARIF) alerts with rule, severity, state, and location.

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": {
      "org": "<org>"
    },
    "name": "list_code_scanning_alerts"
  }
}

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)
`state`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned fields (rule, severity, state, location), which is useful. It says nothing about pagination, result caps, or whether results are filtered to open alerts by default.

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?

A single well-formed sentence with the resource front-loaded and the returned fields trailing; every clause carries information and there is no filler.

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

Completeness3/5

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

For a read-only, two-parameter listing tool with full annotation coverage and no output schema, the essentials are present. Missing are the critical operational details an agent would want: default state filtering, pagination behavior, and any result limits for an org-wide alert listing.

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

Parameters2/5

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

Schema coverage is only 50%: org is documented in the schema, but state has an enum with no description anywhere. The description's mention of "state" appears in the list of returned fields rather than as a filter parameter, so it does not clarify what the state parameter does or what happens when it is omitted. The description therefore fails to compensate for the coverage gap.

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?

States a specific verb and resource ("List the organization's code-scanning (CodeQL/SARIF) alerts") and parenthetically disambiguates the alert type from secret-scanning and Dependabot alerts. It does not name those siblings explicitly, but the CodeQL/SARIF qualifier is enough for an agent to route correctly.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling alert tools (list_secret_scanning_alerts, list_dependabot_alerts) that an agent must choose between. The use case is inferable from the resource name alone, so this is no-guidance rather than misleading.

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