Skip to main content
Glama

estimate_system_capacity

Calculate distributed system capacity from DAU or presets to size QPS, cache-adjusted DB load, storage, bandwidth, Redis RAM, shards, bottlenecks, and peak concurrency.

Instructions

Compute exact back-of-the-envelope distributed systems capacity math: avg & peak Write/Read QPS, cache-adjusted DB QPS, N-year raw & replicated storage, peak ingress/egress Gbps, Redis RAM sizing, primary shard count + dominant bottleneck, and Little’s Law peak concurrency. Supports Big Tech presets (tinyurl, twitter, whatsapp, uber, youtube, stripe) or custom numbers.

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": "estimate_system_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauNoDaily active users.
presetNoOptional preset baseline to start from (any explicit field below overrides the preset).
avgLatencyMsNoExpected average end-to-end latency in ms for Little’s Law.
avgReadBytesNoAverage response payload size in bytes.
avgWriteBytesNoAverage metadata write record size in bytes.
cacheHitRatioNoExpected cache hit ratio 0..0.99 (default 0.8).
peakMultiplierNoPeak-to-average traffic spike multiplier (default 3).
readWriteRatioNoRead-to-write ratio (e.g. 100 for 100:1 read-heavy).
retentionYearsNoData retention window in years (default 5).
replicationFactorNoStorage replication factor (default 3).
mediaBytesPerWriteNoOptional blob/media bytes per write (stored in S3/R2).
writesPerUserPerDayNoAverage write operations per user per day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well by enumerating the outputs: QPS, storage, bandwidth, Redis RAM, shard count, bottleneck, and Little's Law concurrency. It does not explicitly state that the tool is side-effect-free or describe result format/assumptions, but for a pure calculation tool the output disclosure is substantial.

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?

The description is front-loaded with the core purpose and then lists the computed outputs efficiently. It is dense but has no obviously wasted sentences; the long metric list is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter calculation tool with no output schema and no annotations, the description gives a strong output inventory and explains that presets or custom inputs are supported. Remaining gaps are minor, such as not spelling out result structure or modeling assumptions, but the schema fills in parameter defaults and override behavior.

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 12 parameters including defaults and the preset override rule. The description adds only the high-level distinction between presets and custom numbers, which is already reflected in the schema, so baseline 3 is appropriate.

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 states a specific verb, 'Compute', and a specific resource, distributed systems capacity math, then enumerates the exact metrics produced. That makes it clearly distinct from sibling audit, recommendation, and simulation tools, though it does not explicitly name or compare against them.

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?

Usage is implied by the calculation-focused description and by the mention of Big Tech presets versus custom numbers. However, it does not say when to choose this tool over sibling tools such as recommend_architecture or the simulation tools, nor does it state exclusions.

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