armorcode-mcp

Trigger Scan Pull

armorcode_trigger_scan_pull

Create a temporary schedule to trigger a pull scan for PULL tools. Use dryRun mode to preview without actual execution.

Instructions

Create temporary scheduler for PULL tools (e.g. Black Duck). dryRun defaults true.

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": {
      "toolName": "<toolName>",
      "productName": "<productName>",
      "subproductName": "<subproductName>"
    },
    "name": "armorcode_trigger_scan_pull"
  }
}

Input Schema

Name	Required	Description	Default
`dryRun`	No
`toolName`	Yes
`environment`	No
`productName`	Yes
`subproductName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 9, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior. 'Create temporary scheduler' is vague—no info on whether it's safe, destructive, or what side effects occur.

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

Conciseness2/5

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

Extremely short (one sentence) but missing critical information. Conciseness at the expense of clarity.

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

Completeness1/5

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

No output schema, no param descriptions, and minimal behavioral info. Completely inadequate for a 5-param tool.

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

Parameters1/5

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

Schema coverage is 0% and description only mentions dryRun default. No explanation for required params (toolName, productName, subproductName) or optional environment.

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 states it creates a temporary scheduler for PULL tools with an example (Black Duck), which is specific. However, it doesn't differentiate from sibling tools like 'execute_scan' or 'list_scan_schedulers'.

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?

No guidance on when to use this tool vs alternatives. Mentions dryRun default but no context on when to change it or prerequisites.

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

Deploy Server