Skip to main content
Glama

storage_growth

Read-onlyIdempotent

Project storage volume and relative cost over time from ingest, retention, compression, replication, and growth, then suggest tiering thresholds.

Instructions

Project storage volume and relative cost over time from ingest, retention, compression, replication and growth; suggests tiering thresholds.

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": {
      "dailyIngestGB": "<dailyIngestGB>",
      "retentionDays": "<retentionDays>"
    },
    "name": "storage_growth"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo
hotDaysNo
dailyIngestGBYes
retentionDaysYes
compressionRatioNo
replicationFactorNo
monthlyGrowthPercentNo
hotTierPricePerGBMonthNo
coldTierPricePerGBMonthNo

Output Schema

NameRequiredDescriptionDefault
kindNo
seriesNo
sourcesNo
tieringNo
validatedNo
limitationNo
assumptionsNo
limitationsNo
steadyStateNo
finalStoredGBNo
finalStoredTBNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "dailyIngestGB",
      -  "retentionDays",
      -  "monthlyGrowthPercent",
      -  "compressionRatio",
      -  "replicationFactor",
      -  "months",
      -  "hotDays"
      -]New value: +[
      +  "dailyIngestGB",
      +  "retentionDays"
      +]
    • addedOutput schema / properties / limitation
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / sources
      Added value: +{
      +  "type": "array"
      +}
    • addedOutput schema / properties / validated
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. First observedv0.4.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the safety profile is covered. The description adds one genuinely useful behavioral detail: cost is *relative*, not absolute currency, and the tool also emits tiering threshold suggestions. It does not disclose modeling assumptions (steady daily ingest, linear compounding of monthlyGrowthPercent) or units, which matters for a projection tool.

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 dense sentence with the projection target front-loaded and the modeled factors trailing; no filler. It is efficient, though the semicolon-joined output behavior ('suggests tiering thresholds') could be a separate short clause for faster scanning.

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 nine-parameter projection tool with no schema documentation and no output-schema ambiguity to hide behind, the description is too thin — it omits units, defaults, the 24-month default horizon, the tiering cutover semantics, and what 'relative cost' is indexed against. An agent could call it but would likely mis-set several optional parameters.

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 9 parameters, so the description carries the full burden. It names five concepts (ingest, retention, compression, replication, growth) that map to parameters but supplies no units, defaults, or constraints, and leaves months, hotDays, hotTierPricePerGBMonth, and coldTierPricePerGBMonth entirely unmapped — an agent cannot tell that hotDays is a tiering cutoff or that the two price fields are per-GB-month.

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?

Specific verb ('Project') plus a clearly named resource ('storage volume and relative cost over time') and the input dimensions it consumes, so an agent knows exactly what the tool computes. It stops short of distinguishing itself from close siblings such as capacity_plan, cost_model, or finops_unit_economics, which is the only thing keeping it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use conditions, no prerequisites, and no exclusions. With siblings like capacity_plan and cost_model in the same family, an agent has to infer from the name alone whether this is the right tool for a storage sizing question.

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