Skip to main content
Glama
cyntrisec

cyntrisec

by cyntrisec
OverviewSchemaRelated ServersScoreDiscussions
Python

get_unused_permissions

Identify unused IAM permissions to reduce attack surface. Returns permissions grouped by role with reduction percentages based on configurable days of inactivity.

Instructions

    Find unused IAM permissions (blast radius reduction opportunities).

    Args:
        days_threshold: Days of inactivity to consider unused

    Returns:
        Unused permissions grouped by role with reduction percentages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
days_thresholdNo
snapshot_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits but only says 'find' and returns data. No mention of read-only nature, required permissions, or impact on system.

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?

Very short and structured with Args/Returns, but the Returns section is redundant due to output schema. Could add value without becoming verbose.

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

Completeness2/5

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

Despite having output schema, the description is too sparse for an IAM analysis tool, missing context on how results are computed, snapshot usage, or relationship to other tools.

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 coverage is 0%, but description adds meaning for days_threshold ('Days of inactivity'). Snapshot_id is not explained, leaving one parameter undocumented in description.

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 clearly states the tool finds unused IAM permissions for blast radius reduction, with a specific verb and resource. It is distinct from siblings like check_access or get_remediations.

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 guidance on when to use this tool vs alternatives like check_access or get_remediations. The description lacks context on prerequisites, limitations, or use cases.

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/cyntrisec/cyntrisec-cli'

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