armorcode-mcp

Execute Scan

armorcode_execute_scan

Trigger a security scan for a subproduct by specifying tool, environment, and subproduct name; dry run is enabled by default.

Instructions

Trigger scan for subproduct. 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": {
      "subproductName": "<subproductName>",
      "toolName": "<toolName>",
      "environment": "<environment>"
    },
    "name": "armorcode_execute_scan"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The description mentions that 'dryRun defaults true', providing one behavioral detail. However, without annotations, it fails to disclose other important traits such as whether the operation is destructive or has side effects.

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

Conciseness3/5

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

The description is extremely short (two sentences), but it sacrifices completeness. While it is concise, it lacks necessary detail, making it less effective.

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?

The tool has 5 parameters and no output schema or annotations. The description fails to explain the purpose of most parameters, the expected behavior, or the return value, making it highly incomplete.

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?

With 0% schema description coverage, the description only explains the 'dryRun' parameter's default value. The other four parameters (toolName, environment, productName, subproductName) are not described, leaving significant ambiguity.

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 'Trigger scan for subproduct', which is a clear verb and resource. However, it does not differentiate from the sibling tool 'armorcode_trigger_scan_pull', which may have a similar purpose.

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 is given on when to use this tool versus alternatives, nor any prerequisites or conditions for use.

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

Deploy Server