Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_modules

Discover available AWS security scan modules and their descriptions. Read-only operation, no changes to AWS resources.

Instructions

List available security scan modules with descriptions. Read-only. Does not modify any AWS resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerNoCloud provider to scan (default: aws). With huaweicloud, `region` is a Huawei Cloud region ID (e.g. cn-north-4); omit it or pass "all" to scan every region project of the account. Huawei Cloud Phase 1 is single-account (org_mode falls back to the current account with a warning).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / provider
      Added value: +{
+  "description": "Cloud provider to scan (default: aws). With huaweicloud, `region` is a Huawei Cloud region ID (e.g. cn-north-4); omit it or pass \"all\" to scan every region project of the account. Huawei Cloud Phase 1 is single-account (org_mode falls back to the current account with a warning).",
+  "enum": [
+    "aws",
+    "huaweicloud"
+  ],
+  "type": "string"
+}
  2. First observedv0.7.6

TDQS

A4.2/5.0
Behavior4/5

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

The description explicitly states 'Read-only. Does not modify any AWS resources,' which is valuable behavioral disclosure. However, no annotations are provided, so the description carries the full burden; it could add more context about output format or whether it queries live AWS APIs, but the safety guarantee is clearly stated.

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?

Two short sentences with no waste. The core purpose and the read-only guarantee are front-loaded, and every word earns its place.

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?

For a simple list tool with one optional parameter and no output schema, the description is nearly complete. It could mention what the returned list contains (names, descriptions) but the description already says 'with descriptions.' The read-only note covers the main safety concern.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the provider parameter thoroughly. The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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?

The description states a specific verb ('List') and resource ('available security scan modules') and explicitly notes it is read-only. It distinguishes itself from the many sibling scan_* tools by being the listing tool rather than a scanning tool.

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?

The description clearly indicates this is for listing modules, not running scans, and the read-only note implies it is safe to call for discovery. It does not explicitly name alternatives or say when not to use it, but the sibling context makes the distinction clear.

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