Skip to main content
Glama

architecture_pattern

Read-onlyIdempotent

Select a reference architecture by workload pattern and provider to get tradeoffs, clarifying questions, and a Mermaid diagram with equivalent cloud services.

Instructions

Select a reference architecture by explicit workload pattern; returns tradeoffs, questions and Mermaid. provider maps the AWS services to Azure, GCP, OCI or open source equivalents.

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": {
      "pattern": "<pattern>",
      "workload": "<workload>"
    },
    "name": "architecture_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes
providerNoaws
workloadYes

Output Schema

NameRequiredDescriptionDefault
fitNo
kindNo
nodesNo
mermaidNo
sourcesNo
providerNo
servicesNo
workloadNo
questionsNo
tradeoffsNo
validatedNo
limitationNo
serviceMappingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "pattern",
      -  "workload",
      -  "provider"
      -]New value: +[
      +  "pattern",
      +  "workload"
      +]
  2. First observedv0.4.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/no-side-effect, so the bar is lower. The description adds real value by disclosing the response contents (tradeoffs, open questions, Mermaid) and clarifying that provider remaps AWS services to another cloud — behavior not encoded in annotations.

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 tight clauses, front-loaded with the action and selection axis, then output contents, then the provider modifier. No filler, though the provider sentence could be attached more tightly to the parameter it describes.

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?

An output schema exists, so return structure needn't be explained, and the description follows good practice by summarizing it anyway. What's missing is how to choose among the five patterns and how to fill the required workload field — material gaps for a tool whose entire usefulness rests on pattern selection.

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 carry parameter meaning. It explains 'provider' as a cloud remapping selector and ties 'pattern' to workload patterns, but the required free-text 'workload' parameter (up to 4000 chars) is never explained — what to put there is left entirely to inference.

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 ('Select a reference architecture') plus the key input axis ('by explicit workload pattern') and names what comes back. It is distinguishable from diagram-oriented siblings like architecture_diagram and c4_model, though it doesn't explicitly contrast with architect_panel or service_equivalents.

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?

'by explicit workload pattern' implies the trigger condition, and the provider clause implies cross-cloud comparison usage. But no sibling is named, and there is no statement of when-not to use this vs. architect_panel, service_equivalents, or rag_pipeline_plan for the same patterns.

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