Skip to main content
Glama

ArchGuard MCP

estimate_system_capacity

Compute exact distributed systems capacity math: avg/peak QPS, storage, bandwidth Gbps, Redis RAM, shard count & bottleneck, Little's Law concurrency. Supports Big Tech presets or custom inputs.

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
dauNo
presetNo
avgLatencyMsNo
avgReadBytesNo
avgWriteBytesNo
cacheHitRatioNo
peakMultiplierNo
readWriteRatioNo
retentionYearsNo
replicationFactorNo
mediaBytesPerWriteNo
writesPerUserPerDayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose the computed quantities and that the math is "exact" (suggesting a deterministic calculator rather than a sampling simulation). It says nothing about defaults, behavior when inputs conflict, unit conventions, or whether presets override custom fields, which are the traits an agent would need to trust the call.

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 sentences, front-loaded with the verb and the output set; there is essentially no filler. The only quibble is that the metric list is dense and a small amount of space could have been traded for parameter or preset clarification.

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

Completeness2/5

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

For a 12-parameter tool with no annotations, no output schema, and zero schema coverage, this description is far too thin — an agent cannot determine defaults, units, preset override behavior, or the return shape from it. The output list is helpful but the input contract remains largely opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the description must compensate and largely does not: it names the concept of presets and lists output metrics, but never explains what dau, cacheHitRatio, replicationFactor, retentionYears, avgLatencyMs, or the byte fields mean, their units, or their defaults. The critical ambiguity of how a preset interacts with the other 11 parameters is left unaddressed.

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?

Uses a specific verb ("Compute") plus a precise resource ("distributed systems capacity math") and enumerates the concrete outputs: avg/peak QPS, storage, bandwidth in Gbps, Redis RAM, shard count, bottleneck, and Little's Law concurrency. This is enough to distinguish it from siblings like simulate_consistent_hashing or recommend_architecture, but it never names an alternative or states the boundary explicitly, so it falls short of a 5.

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?

"Supports Big Tech presets or custom inputs" implies the two usage modes (pick a preset vs supply your own numbers), which is genuine routing guidance. However, there is no statement of when to choose this tool over the sibling simulators, no prerequisites, and no when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.