Skip to main content
Glama

Usable RAID capacity

bpj_system_raid_capacity
Read-onlyIdempotent

List eligible RAID 0, 1, 5, 6 and 10 capacities for equal-sized drives before filesystem overhead.

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": {
      "drives": "<drives>",
      "driveTiB": "<driveTiB>"
    },
    "name": "bpj_system_raid_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
drivesYes
driveTiBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this a pure, deterministic, side-effect-free read (readOnlyHint, idempotentHint, openWorldHint=false), so the safety profile is fully covered. The one genuinely additive behavioral fact is "before filesystem overhead", which warns the agent that results are raw and will exceed formatted usable capacity. Notably absent is any statement about how "eligible" filtering behaves or what the response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource and the scope constraints front-loaded and no filler. Every clause (levels, equal-sized drives, pre-overhead) carries information.

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 two-parameter read-only calculator this covers the essentials: inputs are implied by the schema and the key caveat is stated. The main gap is that with no output schema, the description never says the response is a per-level capacity breakdown or how ineligible levels are reported.

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 0%, so the schema supplies only titles and min/max bounds. The description partially compensates by saying drives are "equal-sized", which explains why a single driveTiB value stands in for a per-drive list, and "before filesystem overhead" clarifies the unit context. It still does not state that returned capacities share the TiB unit of driveTiB, nor how drive count interacts with level eligibility.

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 gives a specific verb ("List") plus the resource (RAID capacities) and pins the scope to levels 0, 1, 5, 6 and 10 for equal-sized drives. The word "eligible" hints that some levels get filtered by drive count, but the eligibility rule itself is never stated, and there is no explicit differentiation from sibling capacity tools such as bpj_system_shard_capacity.

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 only implied: an agent can infer this is a planning calculator for raw RAID capacity, to be used when sizing arrays. There is no explicit when-to-use/when-not guidance, no statement about what happens with invalid drive counts (e.g., 2 drives on RAID 5), and no named alternative for post-filesystem or formatted capacity.

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.