Skip to main content
Glama
mcp-aws-explorer

mcp-aws-explorer

by hsooligan95

list_resources

Retrieve and filter cloud resources from local mock data across AWS, Azure, GCP, or OCI to inspect inventory by compute, storage, functions, database, or all.

Instructions

List resources for a cloud provider (mock data). Optionally filter by resource kind.

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": "list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoCloud provider to query: 'aws', 'azure', 'gcp', or 'oci'. All datasets are local mock data.aws
resourceTypeNoWhich resource kind to list: 'compute', 'storage', 'functions', 'database', or 'all'. ('s3' and 'lambda' are accepted as legacy aliases for 'storage' and 'functions'.)all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully flags that all results are local mock data (so no real cloud credentials or live calls are involved), but it says nothing about result volume, ordering, or whether an empty list is returned for unknown filters.

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 short sentences, front-loaded with the primary action. The second sentence largely restates what the schema enumerates, so there is minor redundancy, but nothing is bloated.

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

Completeness4/5

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

For a zero-required-parameter list tool with fully documented enums and no output schema, the description covers what is needed to call it correctly and adds the mock-data context. Only the return shape and sibling routing are under-described.

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%, with both parameters enum-documented including the s3/lambda legacy aliases, so the schema already does the explanatory work. The description adds only the loose notion of an optional kind filter and contributes no format or defaulting detail beyond the schema.

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 and resource ('List resources') plus the domain ('for a cloud provider') and the mock-data caveat. The purpose is immediately clear, but it does not explicitly distinguish itself from siblings such as get_resource_detail or find_idle_resources, leaving that differentiation to inference.

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?

The phrase 'Optionally filter by resource kind' implies the browsing use case, but there is no explicit when-to-use vs when-not guidance and no mention of the sibling tools that would be the alternative for drilling into a single resource or finding idle ones.

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