Skip to main content
Glama

recommend_architecture

Generates a Staff-level distributed system architecture blueprint from workload traits, covering database, caching, contention, messaging/CDC, real-time transport, reliability, and case studies.

Instructions

Generate a Staff-level distributed system architecture blueprint (primary database, caching & stampede control, contention strategy, messaging/CDC, real-time transport, reliability guardrails, and matching Big Tech In-The-Wild case studies) from concrete workload traits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_architecture"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataModelNoPrimary data model.
scaleTierNoTarget scale tier.
consistencyNoConsistency requirement.
latencySloMsNoTarget p99 latency SLO in ms (default 100).
realtimeNeedNoReal-time transport need.
contentionLevelNoRow/key lock contention level.
readWriteProfileNoTraffic profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the output's composition (database, caching, contention, messaging/CDC, transport, guardrails, case studies), but says nothing about determinism, whether all inputs are optional with defaults, cost, or any side effects of generation.

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?

A single front-loaded sentence with the verb and deliverable first, then the enumerated output sections. The parenthetical list is dense but each item earns its place by telling the agent what the result contains; the sentence is long but not padded.

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 seven-parameter tool with no output schema, listing the blueprint's sections is a reasonable substitute for return-value documentation. However, it omits that all seven parameters are optional and what defaults produce (e.g., latencySloMs default 100, unspecified enum fields), leaving an agent unsure what a bare invocation yields.

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% with six well-labeled enums, so the schema already documents every parameter. The description adds only the general framing that outputs are derived from those workload traits, with no extra per-parameter meaning (e.g., how contentionLevel or latencySloMs shape the blueprint). Baseline 3 applies.

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?

Names a specific verb ("Generate") and a concrete resource ("Staff-level distributed system architecture blueprint"), then enumerates the sections the blueprint covers, so the agent knows exactly what it produces. It never mentions how it differs from nearby siblings such as estimate_system_capacity or audit_codebase_architecture, so the differentiation is left implicit.

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?

The phrase "from concrete workload traits" hints at the precondition for calling it, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent cannot tell from the description whether this is the right tool versus the capacity-estimation or audit siblings.

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