mcp-aws-explorer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_resourcesA | List resources for a cloud provider (mock data). Optionally filter by resource kind. |
| get_resource_detailB | Get full details for a single resource by name, within one provider's mock dataset. |
| get_cost_summaryA | Summarize mock cost by service for the current month, with the change versus last month. |
| find_idle_resourcesC | Find resources that look idle: resources of any kind not used within the given number of days. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct intent: enumeration (list_resources), single-item lookup (get_resource_detail), aggregate reporting (get_cost_summary), and heuristic analysis (find_idle_resources). The only mild overlap is between list_resources and find_idle_resources, since idle detection is conceptually a filtered listing, but the descriptions make the boundary clear.
All four tools use snake_case verb_noun form (list_, get_, get_, find_) with verbs that reflect the actual operation. No mixed conventions or vague names like 'process' or 'handle'.
Four tools is on the lean side but each earns its place in a read-only exploration surface. There is no padding, though the set is thin enough that one more operation (e.g. listing providers/kinds) would feel natural.
Core read paths are covered (list, detail, cost, idle), which is reasonable for a mock, read-only explorer where write operations are rightly absent. However, there is no way to discover which providers or resource kinds exist, no tag/attribute search, and no cost breakdown per resource, leaving agents to guess valid parameter values.