Skip to main content
Glama

Backup chain storage

bpj_system_backup_chain_storage
Read-onlyIdempotent

Estimate storage for one full backup plus a fixed amount of incremental change per subsequent day.

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": {
      "fullGiB": "<fullGiB>",
      "changedGiB": "<changedGiB>",
      "days": "<days>"
    },
    "name": "bpj_system_backup_chain_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
fullGiBYes
changedGiBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds the key modeling assumption that incremental change is fixed per subsequent day, but it does not clarify day-count semantics or return-value format beyond what annotations provide.

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 front-loaded sentence with no wasted wording. For a simple estimator, this is appropriately sized and easy to scan.

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

Completeness3/5

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

The tool is simple and annotations cover safety behavior, but with no output schema the description should do more to clarify the result and the exact treatment of retained days. It is adequate but leaves meaningful ambiguity for an agent trying to invoke it precisely.

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 description must carry parameter meaning. It maps fullGiB to one full backup and changedGiB to a fixed daily increment, which adds some value beyond the schema titles, but it leaves ambiguity about whether 'days' includes the full-backup day and therefore what the exact formula is.

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 and resource: 'Estimate storage' for a backup chain, and states the model (one full backup plus incremental change per subsequent day). It is clearly distinct from unrelated sibling calculators, though it does not explicitly differentiate itself from other storage-related siblings.

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 backup-chain context: use this when estimating retained backup storage. However, there is no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as compression or capacity calculators.

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.