Skip to main content
Glama
mcp-aws-explorer

mcp-aws-explorer

by hsooligan95

find_idle_resources

Identify idle cloud resources by finding any resource not used within a specified number of days, so you can review unused assets.

Instructions

Find resources that look idle: resources of any kind not used within the given number of days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_idle_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoCloud provider to query: 'aws', 'azure', 'gcp', or 'oci'. All datasets are local mock data.aws
idleDaysThresholdNoDays without use for a resource to count as idle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the core rule (last-use age beyond a threshold) but says nothing about whether the operation is read-only, what fields come back per resource, how 'use' is determined, or that results are limited to local mock data (only the schema's provider param mentions mocks). For a discovery tool with no annotations and no output schema, that is thin.

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 short sentence, front-loaded with the purpose. There is mild redundancy in restating 'resources' twice ('resources that look idle: resources of any kind not used within...'), but nothing extraneous beyond that.

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?

With only two optional, fully described parameters and no output schema, the definition is nearly sufficient, but it never states the shape or meaning of results (e.g., whether cost or last-used dates are included), which an agent needs to plan a follow-up call to get_resource_detail. Adequate, not complete.

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 description coverage is 100%, so provider and idleDaysThreshold are already fully documented including the default of 30 days and the positive-only constraint. The description echoes the days threshold but adds no new meaning such as units, timezone, or how the threshold interacts with the provider's data.

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 gives a specific verb+resource ('Find resources that look idle') and defines the filter criterion as resources of any kind not used within N days, which separates it from a plain inventory listing like list_resources. It stops short of naming any sibling explicitly, and the hedging word 'look' slightly weakens the claim about what is actually returned.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as list_resources or get_resource_detail. The agent must infer that this is the filtered/analysis variant rather than the exhaustive listing, which is a real gap given four sibling tools.

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