Skip to main content
Glama

UAI x402 Security Tools

iam-risk-score

Return a focused AWS IAM risk score and severity summary for a submitted IAM policy document. (REST equivalent: POST /api/v1/iam-risk-score, $0.03)

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

Input Schema

NameRequiredDescriptionDefault
policyTextYesAWS IAM policy JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden. It usefully discloses the REST equivalent and a $0.03 per-call cost, which lets an agent reason about pricing, but it says nothing about severity scales, what fields the 'summary' contains, or whether it is a pure read/compute.

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?

Two sentences with zero filler, and the core purpose is front-loaded ahead of the REST/cost parenthetical. The cost note earns its place for agent budgeting, and nothing is redundant.

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?

For a one-parameter tool with no output schema, the definition covers the input well but leaves the return side vague: the score range, severity tiers, and summary structure are unstated. Given that no output schema exists to compensate, this is a notable but not severe gap.

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

Parameters2/5

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

Schema coverage is 100%, so the schema already documents the single policyText parameter as 'AWS IAM policy JSON'. The description's only addition is calling it a 'policy document', which adds essentially no new meaning beyond the schema baseline, leaving the 3 benchmark unmet.

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 states a specific verb and resource: it returns a risk score plus severity summary for a submitted AWS IAM policy document. That is concrete enough for an agent to know exactly what it produces, though it never names terraform-iam-risk-scan as the adjacent alternative for Terraform-sourced policies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'for a submitted IAM policy document', which scopes the input to an already-extracted policy rather than a repo or Terraform plan. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance, so the agent must infer the boundary from the input type.

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