mcp-github-enterprise

List Dependabot alerts

list_dependabot_alerts

Read-onlyIdempotent

List an organization's Dependabot alerts to review vulnerable dependencies by package, severity, state, and fixing version.

Instructions

List the organization's Dependabot (vulnerable dependency) alerts with package, severity, state, and the fixing version.

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_dependabot_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/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds value by enumerating what each alert record carries (package, severity, state, fixing version), but it says nothing about pagination, result limits, ordering, or the allowlist enforcement implied by the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the resource and scope appear immediately. The trailing field enumeration is slightly list-like but still earns its place as a return-value preview given there is no output schema.

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 two-parameter read tool with no output schema, the description does minimal but adequate work by previewing returned fields. It leaves the filtering semantics of `state`, pagination behavior, and the effect of the org allowlist unexplained, which are the gaps an agent would actually hit when calling it.

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 inline including the GHE_ORG_ALLOWLIST constraint, while `state` has no description beyond its enum values. The description never mentions that `state` acts as a filter, and listing "state" among alert attributes could even read as an output-only field, so it does not 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?

The description gives a specific verb and resource ("List the organization's Dependabot (vulnerable dependency) alerts") and parenthetically scopes it to vulnerable dependencies, which implicitly separates it from the secret-scanning and code-scanning siblings. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 guidance, no mention of when to prefer list_secret_scanning_alerts or list_code_scanning_alerts, and no prerequisite or permission notes. The only usage signal is the implied 'this lists alerts', leaving the agent to infer everything about context.

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