Skip to main content
Glama

BRAINIAC Cloud FinOps

Detect idle compute

cloud-finops_idle-resource-detect

Mark compute idle only when daysObserved meets the supplied minimum and cpuPercent is below the supplied threshold. Missing CPU is not treated as idle. Price $0.04 USDC. POST /api/v1/cloud-finops/idle-resource-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": {
      "resources": "<resources>"
    },
    "name": "cloud-finops_idle-resource-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourcesYes
minimumDaysNo
cpuThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose real behavioral facts: the pricing ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 without running. What it omits is whether 'Mark' means a persisted tag/state change or just a read-only classification, and whether results are paginated or bounded by the 500-resource input cap – a meaningful ambiguity for a tool whose name sounds mutating.

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 short sentences, correctly front-loaded with the classification logic before pricing and transport details. Nothing is redundant, though the endpoint line ('POST /api/v1/...') adds little for an agent that will invoke the tool through the MCP layer.

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 3-parameter detection tool with a nested resource array and no output schema, the description covers the decision rule and payment behavior but never says what comes back – a list of flagged resourceIds, a count, or projected savings – which is the main thing an agent needs to plan the next step.

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 core relationship: minimumDays is compared against each resource's daysObserved and cpuThreshold against cpuPercent. However, nested item fields such as cost and currency are never explained (presumably for savings estimation), and the top-level optionality of minimumDays/cpuThreshold versus required resources is left to the schema.

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 states a specific verb and resource ('Mark compute idle') and, more usefully, the exact classification predicate that makes this tool distinct from a generic cost scan. It never names a sibling such as cloud-finops_unused-storage-detect, so the compute-vs-storage boundary is only implied by the word 'compute'.

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 through the decision rule (resources with enough observation days and low CPU), and the 'missing CPU is not treated as idle' clause tells the agent one case where results will be conservative. There is no explicit when-to-use vs an alternative tool and no statement of prerequisites such as needing a populated resource inventory.

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