Skip to main content
Glama
Sign In
armorcode-mcp

armorcode-mcp

by raviraj-ntp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Severity Stats

armorcode_get_severity_stats

Retrieve severity statistics for a product or subproduct to analyze vulnerability distribution.

Instructions

Severity breakdown for product/subproduct.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "armorcode_get_severity_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNameNo
subproductNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'breakdown', missing behavioral traits like read-only nature, authentication needs, 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.

Conciseness2/5

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

Extremely concise but at the cost of missing essential details; not appropriately sized for 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?

Given no output schema and no parameter descriptions, the tool definition fails to explain what stats are returned (e.g., counts, severity levels), making it severely 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?

Schema description coverage is 0% and the description does not explain the two parameters (productName, subproductName) beyond implying product/subproduct context, adding no meaningful semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Severity breakdown for product/subproduct' indicates the tool provides severity statistics but uses a vague verb ('breakdown') and does not distinguish from similar sibling tools like risk score retrievals.

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 versus alternatives such as risk score tools or other statistics endpoints, nor any exclusions stated.

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

Deploy Server

Other Tools