Skip to main content
Glama
jowhee327

aws-security-mcp

by jowhee327
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

scan_trusted_advisor_findings

Identify AWS security risks by scanning Trusted Advisor findings. Read-only operation, modifies no AWS resources.

Instructions

Run Trusted Advisor Findings security scanner only. Read-only. Does not modify any AWS resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoAWS region to scan (default: server region)
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. Changed1 schema field changedv0.9.0
    • 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

A3.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the full burden of disclosing side effects. It explicitly states 'Read-only' and 'Does not modify any AWS resources,' which is the most critical behavioral trait for a scanner. It does not cover permission needs or output behavior, but the safety profile is clearly disclosed.

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 filler. The tool's purpose and key safety property 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.

Completeness3/5

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

The description covers the core purpose and side effects, and the schema covers parameters. However, with no output schema and no usage guidance among many similar scan tools, the overall context is only minimally adequate for an agent to confidently select and invoke the tool.

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?

The input schema already documents both parameters fully, with 100% coverage including defaults and enum behavior. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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 clearly identifies the action ('Run ... security scanner'), the specific resource (Trusted Advisor Findings), and emphasizes that it is 'only' this scanner. The resource name itself distinguishes it from sibling scan tools, though it does not explicitly contrast with them.

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 when-to-use guidance is provided. With many sibling scan_* tools, the description gives no explicit indication of when Trusted Advisor Findings should be chosen over Security Hub, GuardDuty, Inspector, or others. 'Only' communicates scope, not selection criteria.

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