Skip to main content
Glama

UAI x402 Security Tools

terraform-iam-risk-scan

Scan Terraform for IAM wildcard policies, public S3/RDS exposure, open security groups, broad assume-role trust, and missing encryption hints. (REST equivalent: POST /api/v1/terraform-iam-risk-scan, $0.10)

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": {
      "terraform": "<terraform>"
    },
    "name": "terraform-iam-risk-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudNoOptional cloud provider hint
terraformYesTerraform HCL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full disclosure burden. It usefully adds the REST equivalent endpoint and the $0.10 cost, which are real behavioral facts not in any structured field, but it never states that the operation is read-only, whether the HCL is transmitted or stored, or what the response contains.

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

Conciseness4/5

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

A single front-loaded sentence listing the checks, followed by a compact parenthetical for endpoint and price. Nothing is padded, though the list of five check categories is dense and the pricing parenthetical competes with the core purpose for attention.

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?

There is no output schema and no annotations, so the description is the only source of behavioral information. It conveys what is checked and the cost, but says nothing about the shape of the results (per-resource findings? severity? counts?) or the limits of the scan, leaving an agent unable to predict the response.

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?

Schema coverage is 100% and both parameters are documented in the schema, so the baseline would be 3. The description adds modest value by framing the operation as consuming Terraform HCL, reinforcing the 'terraform' parameter's expected content, and the cloud hint is implicitly covered by the provider enumeration; no syntax or format detail is added beyond that.

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?

States a specific verb (Scan) and resource (Terraform) and enumerates the exact finding categories checked: IAM wildcard policies, public S3/RDS exposure, open security groups, broad assume-role trust, and missing encryption. That is far more specific than a generic 'security scan', but it never distinguishes itself from near-siblings such as iam-risk-score or repo-security-bundle.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative. An agent with both this tool and iam-risk-score or repo-security-bundle in its catalog has no stated basis for choosing between them, so selection must be inferred from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources