Skip to main content
Glama

well_architected_review

Read-onlyIdempotent

Organizes AWS architecture review evidence by six pillars, marking controls without evidence as unknown so they cannot be certified.

Instructions

Organize evidence by six pillars. A met control without evidence is unknown, never certified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workload": "<workload>",
      "controls": "<controls>"
    },
    "name": "well_architected_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
controlsYes
workloadYes

Output Schema

NameRequiredDescriptionDefault
kindNo
nextNo
sourcesNo
summaryNo
controlsNo
workloadNo
validatedNo
limitationNo
missingPillarsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / properties / controls / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / controls / items / required
      Previous value: -[
      -  "id",
      -  "pillar",
      -  "status",
      -  "evidence"
      -]New value: +[
      +  "id",
      +  "pillar",
      +  "status"
      +]
  2. First observedv0.4.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description's job is to add semantics — and it does: a control marked 'met' without supporting evidence is silently reclassified as 'unknown' and never certified. That is a non-obvious transformation rule that directly affects how the agent must populate the input, which is real value beyond the structured fields. It stops short of describing the resulting report or how gaps are aggregated.

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

Conciseness5/5

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

Two tight sentences with no filler, and the evidence/certification rule is stated as a crisp constraint rather than buried in prose. Nothing here is redundant with the name or schema.

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 an output schema and full annotations present, the description needn't explain return values, but for a review tool with a nested controls array it should still clarify what the review produces and where it fits relative to sibling reviewers. The critical evidence rule is covered; the overall scope and outcome are not.

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 0%, so the description must compensate, and it partially does by tying 'evidence' to 'status' and implying pillar bucketing. However, it says nothing about the 'workload' identifier, the owner field, or the 80-control cap, leaving the primary parameters to the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it 'organize[s] evidence by six pillars,' which signals the Well-Architected pillar taxonomy and evidence grouping, but the actual operation is only implied by the tool name ('review'). It never states whether it evaluates, scores, or merely reshapes the supplied controls, and it does not differentiate itself from siblings such as architect_panel or requirements_check.

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 guidance, no prerequisites, and no named alternative among the many architecture-related siblings. The agent must infer invocation conditions entirely from the name and schema.

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