Skip to main content
Glama
DefectDojo MCP Server

DefectDojo MCP Server

Official
by DefectDojo

Finding statistics

get_finding_stats
Read-onlyIdempotent

Count findings by severity and status for a product, engagement, test, product type, or entire DefectDojo instance using exact API counts without retrieving finding text.

Instructions

Count findings by severity and by status for one product, engagement, test, product type, or the whole instance. Uses the API's own counts, so numbers are exact and no finding text is returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_finding_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idNo
product_idNo
product_nameNoExact product name.
engagement_idNo
product_type_idNo
discovered_afterNoOnly findings found after this date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds that counts come from the API itself and are exact, and that no finding text is returned, but says nothing about behavior when no scope argument is supplied or when several scope filters are combined.

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, front-loaded with the counting behavior and grouping dimensions, followed by the exactness/no-text caveat. No filler or redundancy.

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?

Output schema exists, so return values need not be spelled out, and the description already characterizes the result as counts by severity and status. The remaining gap is filter-combination semantics and the default scope, which matter for a tool with six all-optional parameters.

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 coverage is only 33% (product_name and discovered_after are the only documented parameters), so the description carries extra burden. It partly compensates by mapping the scope arguments to product/engagement/test/product type/instance, but never mentions discovered_after and gives no guidance on whether the six optional filters combine conjunctively or are mutually exclusive — a real ambiguity for an agent.

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 ('Count') and resource ('findings') plus the two grouping dimensions (severity, status) and the scope options, which cleanly distinguishes it from list_findings, which returns finding text.

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?

Gives clear usage context by enumerating the five valid scopes (product, engagement, test, product type, whole instance) and implicitly rules out the list tools via 'no finding text is returned.' It stops short of explicitly naming a sibling or stating when-not to use it.

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