Skip to main content
Glama
ckq-aws

Resilience Architect MCP

by ckq-aws
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

CreateResourceExplorerView

Creates a Resource Explorer view to find and filter resources for fault injection experiments.

Instructions

Create a Resource Explorer view.

This tool creates a new Resource Explorer view that can be used to find
and filter resources for fault injection experiments.

Args:
    ctx: The MCP context for logging and communication
    query: Filter string for the view
    view_name: Name of the view
    name: Required name for the view (will be added as Name tag)
    tags: Optional additional tags to apply to the view
    scope: Scope of the view
    client_token: Client token for idempotency

Returns:
    Dict containing the created view details

Raises:
    Exception: For AWS API errors or when writes are disabled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRequired name for the view (will be added as Name tag)
tagsNoOptional additional tags to apply to the view
queryYesFilter string for the view
scopeNoScope of the view
view_nameYesName of the view
client_tokenNoClient token for idempotency

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two useful traits: the operation can fail 'when writes are disabled' and supports idempotency via client_token. However, it says nothing about required permissions, whether the write is destructive/reversible, or rate limits, so the behavioral picture is only partly filled in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, which is good, but the Args section duplicates the 100%-covered schema verbatim and adds little, while Returns/Raises are genuinely informative. Overall it is somewhat padded for a six-parameter tool.

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?

For a mutation tool with six parameters, no annotations, and no output schema, the description usefully states the return shape and the write-disabled failure mode. It still leaves gaps: no explanation of what a 'scope' or 'query' filter actually accepts, and no guidance on where the created view can be referenced.

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 the schema already documents all six parameters. The Args block merely restates those same descriptions (query, view_name, name, tags, scope, client_token) without adding format, default, or constraint 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?

The description gives a specific verb+resource ('Create a Resource Explorer view') and ties the view to a concrete purpose: finding and filtering resources for fault injection experiments. It implicitly distinguishes itself from the read-side sibling ListResourceExplorerViews, though it never names that sibling explicitly.

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?

It says the created view is for fault-injection resource filtering, which implies a context, but it never states when to create a new view versus reuse/list an existing one, nor does it name ListResourceExplorerViews as the alternative. No when-not conditions or prerequisites are given.

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

Deploy Server

Other Tools