Skip to main content
Glama
OmniNomadLLC

aws-audit-mcp

by OmniNomadLLC

audit_full_posture

Read-only

Run all AWS security audit checks in one pass and aggregate findings into a single account posture report, including severity counts, weighted posture score, grade, and errors.

Instructions

Run every registered audit check with default arguments and aggregate the results into a single account posture report.

Discovers all audit_*/account_* functions in the tool modules and runs each one; a failing check is recorded in errors and never aborts the rest. Returns the standard {check, ok, findings, scanned} envelope where findings is the concatenation of every sub-report's findings and scanned is the number of checks run, plus severity_counts (LOW/MEDIUM/HIGH/CRITICAL), posture_score, grade, checks_run, and errors. The score is weighted: each CRITICAL finding costs 10 points, HIGH 5, MEDIUM 2, LOW 1, and posture_score = max(0, 100 - total weight). Grades: A >= 90, B >= 75, C >= 60, D >= 40, else F.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds substantial behavioral detail: failing checks are captured in errors without aborting, the exact response envelope is specified, and the scoring/weighting model is fully explained. This exceeds what annotations convey.

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?

The description is well-structured: the core behavior is front-loaded, followed by the run semantics, return envelope, and scoring rules. Every sentence adds necessary information for correct invocation and interpretation, with no filler.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description fully covers invocation behavior, error handling, return structure, scoring weights, and grade thresholds. An agent has everything needed to call the tool and interpret its result.

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

Parameters4/5

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

The tool has zero parameters, and the schema covers 100% of them by having none. Per baseline, no parameter documentation is needed; the description correctly focuses on behavior and output rather than adding meaningless parameter detail.

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?

States a specific verb ('Run every registered audit check') and a concrete deliverable (aggregated account posture report). It clearly distinguishes itself from the sibling tools by describing the aggregation of all audit/account functions rather than a single check.

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 implies when to use this tool (when a full account-wide posture report is needed, as opposed to a specific audit_* sibling) and details what coverage includes. It lacks explicit 'use this instead of X' phrasing but provides clear contextual guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OmniNomadLLC/aws-audit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server