Amazon Managed Prometheus MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all Amazon Managed Prometheus workspaces in the specified region. Args: region: AWS region to query (default: us-east-1) Returns: JSON string containing list of workspaces with their details |
| get_workspaceC | Get detailed information about a specific Amazon Managed Prometheus workspace. Args: workspace_id: The ID of the workspace to retrieve region: AWS region where the workspace is located (default: us-east-1) Returns: JSON string containing workspace details |
| query_metricsA | Execute a PromQL query against an Amazon Managed Prometheus workspace. Args: workspace_id: The ID of the workspace to query query: PromQL query string region: AWS region where the workspace is located (default: us-east-1) start_time: Start time for range queries (RFC3339 format) end_time: End time for range queries (RFC3339 format) step: Query resolution step for range queries (e.g., "15s", "1m") Returns: JSON string containing query results or preparation details |
| get_workspace_statusB | Get the current status of an Amazon Managed Prometheus workspace. Args: workspace_id: The ID of the workspace region: AWS region where the workspace is located (default: us-east-1) Returns: JSON string containing workspace status information |
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 has a clearly distinct purpose: list_workspaces enumerates all workspaces, get_workspace retrieves detailed information, get_workspace_status checks status, and query_metrics executes PromQL queries. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case: list_workspaces, get_workspace, get_workspace_status, and query_metrics. The naming is predictable and readable throughout.
Four tools is reasonable for a focused Prometheus monitoring server, covering core operations like listing, retrieving, checking status, and querying. It might be slightly thin for full CRUD operations, but it aligns well with the server's purpose.
The tools cover read and query operations effectively, but there are notable gaps in write operations (e.g., create, update, or delete workspaces). This limits agents to monitoring and querying without management capabilities, which could be a constraint for full lifecycle workflows.