Skip to main content
Glama

BRAINIAC Cloud FinOps

Detect cost anomalies

cloud-finops_cost-anomaly-detect

Score daily totals with a sample z-score. A day is flagged when the absolute z-score is at least 3 and at least 8 days were supplied. Fewer days are not scored. Price $0.04 USDC. POST /api/v1/cloud-finops/cost-anomaly-detect. Unpaid calls return 402 and do not run.

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": "cloud-finops_cost-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
rowsNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does unusually well on operational traits: it discloses the algorithm, the exact threshold rule, the minimum-data cutoff, the price ($0.04 USDC), and that unpaid calls return 402 without running. It says nothing about how rows/csv/file inputs are reconciled, how daily totals are aggregated, or what the response contains.

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, front-loaded with the scoring rule, then the operational facts. No filler, though the phrasing is telegraphic in places ('Fewer days are not scored') and the endpoint string is of marginal value to an agent.

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

Completeness5/5

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

Given a four-parameter tool with nested objects, zero schema documentation, no output schema, and no annotations, the description is not complete. Missing return shape and input-mode precedence force the agent to guess how to format a call and what comes back.

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% across four parameters, including a nested file object and a 5000-item rows array, so the description carries the burden. It only implies that rows need dates (via 'daily totals' and 'days supplied') and never explains the three input modes (csv, file, rows) or the currency parameter.

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 names a specific method and outcome: 'Score daily totals with a sample z-score,' with a day flagged at |z| >= 3. That is concrete enough to distinguish it from statistical siblings like budget-variance-analyze or monthly-cost-forecast, though it never names an alternative explicitly.

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?

It gives a real precondition — 'Fewer days are not scored' / 'at least 8 days were supplied' — which tells the agent when the tool is useless. It also flags the payment gate. But there is no guidance on choosing this over budget-variance-analyze or cost-optimization-report for related spend questions.

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