io.github.AIops-tools/ceph-aiops

capacity_forecast

Read-only

Estimates days until Ceph capacity reaches 85% using observed daily byte growth, or shows usage-only when growth is omitted for deterministic planning.

Instructions

[READ] Capacity usage + a deterministic days-to-nearfull projection.

Pass an observed daily growth in bytes to get daysToNearfull; without it the forecast is "insufficient-data". Nearfull is 85% of total. No clock is read — the projection is pure arithmetic.

Args: daily_growth_bytes: Observed daily growth in bytes; omit for a usage-only view. target: Ceph target name from config; omit for the default.

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

Input Schema

Name	Required	Description	Default
`target`	No
`daily_growth_bytes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.11.5Sep 19, 2026
Removedv0.3.0Jul 17, 2026
First observedv0.1.0Jul 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety bar is lower; the description adds genuinely useful context beyond that: nearfull is 85% of total, no clock is read, and the projection is pure arithmetic, plus the 'insufficient-data' fallback state. It does not discuss pagination or response shape, but those are minor here.

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?

Front-loaded with the [READ] marker and the core purpose, followed by the arithmetic caveat and an Args section. No sentence is wasted, though the Args block partly mirrors parameter names already visible in the schema.

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?

With no output schema, the description does explain the key return concepts (daysToNearfull, 'insufficient-data') and the nearfull threshold. It is complete enough to call correctly, though it could say more about the usage payload returned by default.

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

Parameters4/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 the parameter burden, and it does: both daily_growth_bytes ('observed daily growth in bytes; omit for a usage-only view') and target ('Ceph target name from config; omit for the default') get meaning and default behavior beyond the bare schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: '[READ] Capacity usage + a deterministic days-to-nearfull projection.' No sibling tool (osd_df, pool_df, cluster_status) does capacity forecasting, so an agent can identify this tool's distinct role immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states clear conditional context: passing daily_growth_bytes yields daysToNearfull, omitting it yields 'insufficient-data' and a usage-only view. It does not name competing siblings or exclusions, which keeps it at 4 rather than 5.

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