Skip to main content
Glama

BRAINIAC Cloud FinOps

Detect unused storage

cloud-finops_unused-storage-detect

Mark a volume unused only when the supplied days meet minimumDays and the volume is unattached or usedGb is 0. Attachment alone is not usage. Price $0.04 USDC. POST /api/v1/cloud-finops/unused-storage-detect. Unpaid calls return 402 and do not run.

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": {
      "volumes": "<volumes>"
    },
    "name": "cloud-finops_unused-storage-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumesYes
minimumDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.04 USDC price, the 402 failure mode that aborts execution, and the non-obvious semantic that attachment alone does not count as usage. It omits what the response looks like and whether any state is persisted by "mark," which for a no-output-schema tool is the main remaining gap.

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?

Four dense sentences with the decision rule front-loaded ahead of pricing and transport details, which is the right ordering. The endpoint path and 402 note are low-value boilerplate but short enough not to hurt scanability.

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?

For a paid detector with a nested 500-item array input, no output schema, and no annotations, the definition covers invocation but not results. An agent knows the eligibility rule and cost but not what it receives back, so the definition is adequate yet short of complete.

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 compensate, and it does explain the relationship between minimumDays and the per-volume days observed plus the attached/usedGb test. However, the nested volume fields cost, currency, and storageGb are left entirely unexplained by both schema and description, and the volumes array itself is not characterized beyond the implicit shape.

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?

States a specific verb and resource ("Mark a volume unused") and pins down the classification rule: days must meet minimumDays and the volume must be unattached or have usedGb of 0. It is clearly a storage-specific detector, but it never references its nearest sibling idle-resource-detect, so the agent must guess at the boundary between the two.

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?

The description gives the internal decision rule rather than guidance on when to call this tool versus the other finops detectors. The only operational guidance is that unpaid calls return 402 and do not run, which tells the agent a payment gate exists but not when this detector is the right pick.

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.

Resources