Skip to main content
Glama
inspicere

mcp-defectdojo

by inspicere

reimport_scan

Upload a scan report to an existing DefectDojo test, with options to close outdated findings, deduplicate, and auto-create product or engagement if needed.

Instructions

Re-import a scan report into an existing test in DefectDojo. Requires write scope. Rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesBase64-encoded scan result file content.
tagsNoList of tags to apply.
activeNoMark imported findings as active (default True).
test_idNoExisting test ID to reimport into (> 0).
versionNoVersion string for the scan.
build_idNoBuild identifier.
group_byNoGrouping strategy (e.g. "component_name+component_version").
verifiedNoMark imported findings as verified (default False).
file_nameYesOriginal filename of the scan result.
scan_typeYesScanner type (e.g. "Semgrep JSON Report", "Trivy Scan", "ZAP Scan").
branch_tagNoBranch or tag name.
commit_hashNoCommit hash.
product_nameNoProduct name (required when auto_create_context is True).
push_to_jiraNoPush findings to Jira (default False).
engagement_nameNoEngagement name (required when auto_create_context is True).
minimum_severityNoMinimum severity to import (Critical/High/Medium/Low/Info).
do_not_reactivateNoDon't reactivate previously closed findings (default False).
product_type_nameNoProduct type name for auto-creation.
close_old_findingsNoClose findings not present in this scan (default True).
auto_create_contextNoAuto-create product/engagement if they don't exist (default True).
deduplication_on_engagementNoDeduplicate within the engagement (default True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. The description adds 'Requires write scope' and 'Rate-limited', but doesn't disclose other behaviors like impact on existing findings, which is covered by parameters but not described.

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 concise sentences, front-loaded with the main action. No extraneous information.

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?

Given the 21 parameters and output schema, the description covers the core action but misses some nuance about the reimport process (e.g., updating vs overwriting). Still mostly complete.

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?

With 100% schema coverage, the description adds no extra parameter meaning beyond the schema definitions. 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?

The description clearly states the action (re-import), the resource (scan report into existing test), and the context (DefectDojo). It is specific enough to distinguish from import_scan.

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?

It indicates when to use (re-import into existing test) and prerequisites (write scope, rate-limit), but doesn't explicitly state when not to use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inspicere/mcp-defectdojo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server