Skip to main content
Glama
drewrukin

dtrack-mcp

by drewrukin

set_analysis

Update analysis record for a vulnerability finding. Set state, justification, response, details, comment, or suppression using component and vulnerability UUIDs or a finding dict.

Instructions

⚠ WRITE. Update the analysis record for one finding.

Two ways to identify the finding:

  • Pass component_uuid and vulnerability_uuid directly.

  • Pass finding — a NormalizedFinding dict as returned by list_findings, group_findings_by_alias, or entries inside find_duplicate_analyses. The UUIDs are extracted automatically, avoiding copy-paste errors in the triage loop.

When finding is provided, its UUIDs take precedence. project_uuid is always required because findings from find_duplicate_analysesother_projects may belong to a different project.

Issues PUT /api/v1/analysis; the connection-layer guard refuses any other write path. Fields left as None are omitted from the body, so DT keeps its current value. comment appends to the history, it does not replace existing comments. Returns the full normalized analysis after the write.

Args: project_uuid: DT project UUID. state: One of NOT_SET, IN_TRIAGE, EXPLOITABLE, FALSE_POSITIVE, NOT_AFFECTED, RESOLVED. component_uuid: DT component UUID (required unless finding is provided). vulnerability_uuid: DT vulnerability UUID (required unless finding is provided). finding: A NormalizedFinding dict. When provided, component_uuid and vulnerability_uuid are extracted from it. justification: Optional CycloneDX justification enum (e.g. CODE_NOT_REACHABLE, REQUIRES_CONFIGURATION). response: Optional response enum (e.g. CAN_NOT_FIX, WILL_NOT_FIX, UPDATE, ROLLBACK, WORKAROUND_AVAILABLE). details: Optional free-text analysis details. comment: Optional free-text comment appended to the history. suppressed: Optional bool to suppress/unsuppress the finding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidYes
stateYes
component_uuidNo
vulnerability_uuidNo
findingNo
justificationNo
responseNo
detailsNo
commentNo
suppressedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses write nature (⚠ WRITE), HTTP method (PUT), behavior of None fields (omitted) and comment appending, and return value. No annotations provided, so description carries full burden; could mention error handling or rate limits.

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?

Well-structured with sections, bullet points, and arg list. Front-loaded with purpose and warning. Slightly long but justified by 10 parameters; every sentence adds value.

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?

Covers purpose, usage, parameters, behavioral details, and return value. Output schema exists so return description is sufficient. Could include error scenarios or idempotency, but overall comprehensive for a write tool.

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

Parameters5/5

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

Every parameter explained with context: relationships between component_uuid, vulnerability_uuid, and finding, enum examples, optionality. Adds significant meaning beyond the schema which has 0% description coverage.

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?

Description explicitly states 'Update the analysis record for one finding' with clear verb-resource pair. Distinguishes from siblings by specifying the write path and mentioning alternative finding identification methods.

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?

Provides two explicit ways to identify the finding with precedence rules, explains why project_uuid is always required, and notes field omission behavior. Lacks direct contrast with sibling tools for when not to use.

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/drewrukin/dtrack-mcp'

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