Skip to main content
Glama
drewrukin

dtrack-mcp

by drewrukin

broadcast_triage

Propagate a triage decision from a reference version to all other versions of the same product, eliminating the need to repeat the operation for each version.

Instructions

⚠ WRITE (when mode="exact"). Fan out triage decisions to all versions.

A specialised form of carry_over_triage for the case where a new CVE is found simultaneously in multiple versions of the same product. Instead of running carry_over N times, triage the finding once in any version, then call this tool to propagate the decision in all directions (newer AND older versions).

Steps:

  1. Fetches every version of project_name from DT.

  2. Excludes the reference version.

  3. Calls carry_over_triage(reference → target) for each.

  4. Returns per-target results plus an aggregate summary.

ALWAYS run mode="dry_run" first to review the plan.

Args: reference_project_uuid: UUID of the version that already has the triage decision to broadcast. project_name: Exact project name (used to find all other versions). mode: "dry_run" (no writes) or "exact" (performs writes). include_updated_components: Also transfer updated_component matches. Default False — conservative. overwrite_not_set: Transfer over targets in state NOT_SET. Default True. overwrite_any: Transfer over targets in any state. Default False. comment_prefix: Prepended to every carry-over comment. max_operations: Per-target cap. Raise if a single target needs more. active_only: Skip inactive/archived versions. Default True.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_project_uuidYes
project_nameYes
modeNodry_run
include_updated_componentsNo
overwrite_not_setNo
overwrite_anyNo
comment_prefixNo[dtrack-mcp]
max_operationsNo
active_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses it is a WRITE operation when mode='exact', describes the full algorithm (fetch, exclude, iterate, return), and covers default behaviors without contradiction.

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?

Well-structured with warning, purpose, steps, and parameter docs; every sentence is valuable and front-loaded with critical info.

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

Completeness5/5

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

Given no annotations, 9 parameters, and output schema present, the description fully covers behavior, usage, and parameter details, making it self-sufficient for an AI agent.

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?

Despite 0% schema coverage, the description provides detailed explanations for all 9 parameters, including defaults and behavior, far exceeding schema information.

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?

Clearly states 'Fan out triage decisions to all versions' and distinguishes from sibling 'carry_over_triage' as a specialized form for simultaneous CVEs across versions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises to always run dry_run first, compares to carry_over_triage, and provides step-by-step usage guidance.

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